Skip to main content
Glama

Update project

update_project
Idempotent

Rename a project

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": {
      "name": "<name>"
    },
    "name": "update_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
project_idNoProject id (or use session from use_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds no behavior of its own: it does not say whether renaming affects the project's domains, URLs or share links, what happens on a name collision, or that the 60-character limit from the schema is enforced. For a mutation on a resource with derived identifiers, that silence matters.

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

Conciseness3/5

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

Three words, front-loaded and free of waste, but the terseness is under-specification rather than disciplined concision for a write tool. There is room for one more short clause about the target field or identifier without bloat.

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

Completeness2/5

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

The tool is simple (two parameters, no output schema) and annotations cover idempotency and safety, so a short description is defensible. Still, the description leaves the required parameter's meaning implicit and says nothing about side effects on domains or links, which is exactly the information an agent needs before mutating a project.

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

Parameters3/5

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

Schema coverage is 50%: project_id is documented in the schema, but the required 'name' parameter has no schema description. The description's 'rename' implies name is the new project name, which is a genuine clarification, though it does not address uniqueness, format, or the session fallback for project_id.

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

Purpose4/5

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

"Rename a project" gives a concrete verb and resource, and usefully narrows the broader-sounding name update_project to a single field change, which separates it from create_project, delete_project and get_project. It stops short of stating the target field is the 'name' parameter or how the project is identified.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of the session-vs-project_id selection path that the schema hints at with 'or use session from use_project'. The agent must infer everything about invocation context from the sibling list and schema.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources