Skip to main content
Glama

ai_modeling_canvas_template_get

Read-only

Retrieve a single Canvas template graph by ID to inspect its structure, nodes, and connections for reuse or analysis.

Instructions

Read one Canvas template graph.

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

Input Schema

NameRequiredDescriptionDefault
idYes

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 nothing beyond that: it does not say whether the full graph is returned, whether missing ids raise an error, or what the open-world fetch implies, so it contributes no behavioral context of its own.

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?

It is a single front-loaded sentence with no wasted words, which is structurally clean. But the brevity crosses into under-specification rather than earned conciseness for a tool that needs at least its identifier explained.

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

Completeness1/5

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

With no output schema and 0% parameter coverage, the description is the only place an agent could learn what comes back and what the id means. It supplies neither, so an agent cannot reliably invoke this tool correctly from the definition alone. A single clause naming the identifier and the returned graph would have closed the gap.

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 single required parameter id has no documented meaning anywhere. The description never states that the parameter is the template identifier, nor explains the accepted character pattern or length limits, leaving the agent to guess from the schema constraint alone.

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?

"Read one Canvas template graph" gives a clear verb (Read) and resource (Canvas template graph), and "one" signals single-item retrieval rather than a list. However, it does not distinguish this template graph fetch from nearby siblings such as ai_modeling_canvas_template_source or ai_modeling_canvas_get, and "graph" is left undefined.

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 alternatives, no prerequisites, and no mention of what happens if the id is unknown. The agent must infer usage entirely from the name.

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