Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

Rename project

rename_project

Rename a project, and optionally change its description (the twin of ankra project rename). Needs projects.manage. The slug never changes. project_id comes from list_projects.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "name": "<name>"
    },
    "name": "rename_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe new display name, at most 128 characters.
project_idYesUUID of the project (from list_projects).
descriptionNoA new description, at most 2048 characters; omit to keep the current one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare the write/safety profile, and the description adds real context beyond them: the required permission scope and the important invariant that the slug never changes. It does not cover failure modes (duplicate names, max length violations) or what the response returns, which keeps it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short clauses, all front-loaded: operation and scope first, then permission, invariant, and parameter provenance. Nothing is padded; even the CLI-twin parenthetical is brief and oriented toward agents familiar with the CLI.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter mutation with fully documented schema and clear annotations, the description covers permission, scope of change, and parameter sourcing. With no output schema, a sentence on what is returned or confirmed would round it out.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description adds meaning on top: 'the slug never changes' clarifies that 'name' is display-only, and 'project_id comes from list_projects' names the discovery tool. The optional description parameter's effect is described in the schema but echoed usefully.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Rename a project') plus the exact secondary effect ('optionally change its description'), which distinguishes it from rename_stack, rename_ai_endpoint, update_stack, and other update-shaped siblings. An agent can identify the operation without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a prerequisite ('Needs projects.manage') and routes the agent to the source of the key input ('project_id comes from list_projects'). It does not state when to prefer update-style siblings or what to do when the caller lacks the permission, so it stops short of explicit alternatives/exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ankra toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources