Skip to main content
Glama

ai_modeling_canvas_get_project

Read-only

Inspect a Canvas project by project ID and return its canvas ID, letting agents retrieve project context before generating, editing, or managing Canvas assets.

Instructions

Inspect a Canvas project and its canvas ID.

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": "ai_modeling_canvas_get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the hint that a canvas ID is surfaced; it says nothing about permissions, whether the project must exist, or what happens if the ID is invalid.

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?

One short sentence with no filler, and the subject (project plus its canvas ID) is front-loaded. It is efficient, but the terseness borders on under-specification rather than genuine crispness.

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 read tool with one required identifier and no output schema, the description should at least say what identifying information is needed and what the inspection returns. Neither is provided, leaving the agent to guess how this differs from the sibling getters.

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% for the single required parameter projectId, and the description never mentions it. It does not explain the accepted identifier format (the schema's pattern allows colons, underscores, dots) or where an agent should obtain a projectId.

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

Purpose3/5

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

The description names a resource ('Canvas project') and a vague verb ('Inspect'), plus hints that a canvas ID is returned. It does not distinguish this from closely named siblings such as ai_modeling_canvas_get or ai_modeling_project_get, so an agent cannot confidently tell which one to pick.

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

Usage Guidelines1/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 alternatives. The single sentence gives no condition under which this tool should be chosen over the many other canvas/project getters in the catalog.

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