Skip to main content
Glama

ai_modeling_canvas_append_template

Append a template to a Canvas project by supplying a project ID and template ID, enabling agents to add Canvas assets through the ai-modeling MCP server.

Instructions

Append a template to 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>",
      "templateId": "<templateId>"
    },
    "name": "ai_modeling_canvas_append_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes
templateIdYes

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 declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is known. The description adds nothing beyond that: no statement about whether appending is idempotent, what happens if the template is already in the project, whether existing nodes are preserved, or what permission scope is needed for a mutating, open-world call.

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?

A single front-loaded sentence with zero waste, which is structurally clean. However, its brevity is achieved by omission rather than economy, so it reads as under-specified rather than tight.

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 mutating, open-world tool with two required but entirely undocumented parameters and no output schema, the definition leaves too much unstated. An agent cannot tell what it needs to supply, what will change, or what it gets back.

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% and the description does no work to compensate: it never names projectId or templateId, nor their formats, constraints, or accepted ID forms. Only the surface nouns 'template' and 'Canvas project' loosely hint at the two inputs, leaving both effectively undocumented.

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?

States a concrete verb + resource + target: 'Append a template to a Canvas project.' An agent can picture the operation without opening the schema. It stops short of a 5 because it never differentiates from the sibling 'ai_modeling_canvas_from_template', which plausibly covers the same template-to-project territory.

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?

Provides no when-to-use guidance, no prerequisites, and no mention of the closest alternative ('from_template') so the agent must guess which one applies. The only usage signal is the word 'append', which is not defined against any sibling.

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