Skip to main content
Glama

ai_modeling_canvas_rename

Rename a Canvas project by providing its project ID and a new name, keeping project labels organized and easy to identify.

Instructions

Rename a Canvas 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": {
      "projectId": "<projectId>",
      "name": "<name>"
    },
    "name": "ai_modeling_canvas_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so safety framing is covered. The description adds nothing beyond that: it does not say whether the rename affects share links, whether names must be unique, whether the old name is recoverable, or what happens on failure.

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

Conciseness4/5

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

A single five-word sentence with zero padding and the action front-loaded. Its brevity is efficient, though it is economical to the point of omitting information the agent needs.

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?

For a mutation tool with no output schema and two completely undocumented parameters, the definition should explain scope, constraints, and error behavior. What is present is accurate but far from sufficient to call it confidently against near-identical siblings.

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 description carries the burden of explaining the two required parameters and does not: no mention of projectId format/scope or the name constraints beyond what the raw schema's minLength/maxLength/pattern imply. Only the self-evident parameter names ('name', 'projectId') provide any meaning.

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?

The description uses a specific verb and resource ('Rename a Canvas project'), so an agent knows this mutates a project's name rather than its contents. It does not distinguish itself from the sibling 'ai_modeling_project_rename', leaving ambiguity about which rename target applies to a given object.

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 tool versus the closely named 'ai_modeling_project_rename' or any canvas retrieval/mutation siblings. No prerequisites, no exclusions, and no statement of what state the project must be in.

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