Skip to main content
Glama

ai_modeling_project_rename

Renames an existing Studio project using its project ID and a new name, so you can update project labels without changing the project contents.

Instructions

Rename your Studio 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_id": "<project_id>",
      "name": "<name>"
    },
    "name": "ai_modeling_project_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already disclose readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that — no mention of whether the rename is persistent, what happens to the old name, or whether concurrent edits conflict. For a mutation tool, that is a thin contribution even against the lower annotation-backed bar.

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?

The single short sentence is front-loaded and free of waste, but it is under-specified rather than concise. Five words is not an appropriate size for a two-required-parameter mutation tool.

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?

With no output schema, no parameter descriptions, and a mutation that must be identified by ID, an agent needs to know the identifier format and expected result. The description supplies neither, leaving it materially incomplete for the tool's complexity.

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

Parameters2/5

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

Schema description coverage is 0%, so the schema names project_id and name with constraints (length limits, a character pattern) but explains none of them. The description does not compensate at all — it never states that a project identifier and a 1–100 char new name must be supplied.

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 your Studio project" gives a specific verb (rename) and a specific resource (project), so the operation is unmistakable. It does not distinguish itself from siblings such as ai_modeling_canvas_rename or ai_modeling_motion_rename, which is the only thing keeping it from a 5.

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 guidance on when to use this versus the canvas or motion rename tools, no prerequisites, and no note about required ownership or permissions. The agent must infer all of this from the tool name alone.

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

Deploy Server

Other Tools