Skip to main content
Glama

Update project

update_project

Change a project's name, slug, description or kind (general, film, game, ads, app). project is its id or slug. Only the fields given are changed; an empty description clears it. Returns the updated 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": {
      "project": "<project>"
    },
    "name": "update_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
nameNo
slugNo
projectYes
descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description's value-add is the mutation semantics: partial update behavior and the notable edge case that an empty `description` clears the field. That clearing behavior is real destructive detail not derivable from the annotations. It stops short of stating slug-uniqueness collisions or permission requirements for a mutating call.

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?

Three tight sentences, front-loaded with the action and fields, then the identifier semantics, then the mutation/return behavior. Nothing is repeated from the schema and no sentence is filler.

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?

With an output schema present, the description needn't explain return values, and it still gives a one-line confirmation ('Returns the updated project'). For a 5-parameter mutation, the remaining gap is operational context such as authorization or slug collision behavior, but what an agent needs to call it correctly is essentially covered.

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

Parameters5/5

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

Schema description coverage is 0%, so the description fully carries the burden and does so: it names each mutable field, enumerates valid `kind` values (general, film, game, ads, app), and explains that `project` accepts an id or a slug. It also resolves the null-default ambiguity by saying omitted fields are left unchanged.

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 (change) and resource (project) plus the exact set of mutable fields (name, slug, description, kind) with the enumerated kind values. The mutation verb alone separates it from create_project and list_projects without needing to name them.

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

Usage Guidelines3/5

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

Usage is implied by 'Only the fields given are changed' and the clarification that `project` is an id or slug, which tells the agent how to invoke it. However, there is no explicit when-to-use/when-not guidance, no mention of prerequisites such as ownership or permissions, and no routing to siblings like create_project for new projects.

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