Skip to main content
Glama

ai_modeling_canvas_template_create

Snapshot a saved Canvas graph into a reusable template with optional revision guarding, and check template-source before retrying an unknown response.

Instructions

Snapshot the saved Canvas graph into a reusable template, optionally guarding its revision. On an unknown response, query template-source before retrying; the template may be visible in the catalogue.

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": {
      "sourceProjectId": "<sourceProjectId>",
      "sourceCanvasId": "<sourceCanvasId>",
      "scenarioId": "<scenarioId>"
    },
    "name": "ai_modeling_canvas_template_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
revisionNo
scenarioIdYes
sourceCanvasIdYes
sourceProjectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description explains that the operation snapshots a saved graph, that revision can act as a guard, and that an unknown response may mean the template already exists in the catalogue. The 'query before retrying' warning is valuable duplicate-prevention context. It stops short of permission or naming-conflict behavior, so it is not a 5.

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

Conciseness5/5

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

Two sentences, front-loaded with the action and followed by a focused retry caveat. There is no redundant restatement of the name or annotations, and the structure keeps the core action visible first.

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 five-parameter mutation with no output schema and zero schema description coverage, the definition lacks essential input semantics. It covers purpose and retry safety but not what the required sourceProjectId, sourceCanvasId, or scenarioId represent, so an agent could understand the action yet still be unable to populate the call confidently.

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 must explain the five inputs. It only gives semantics for revision ('optionally guarding its revision') and leaves sourceProjectId, sourceCanvasId, scenarioId, and name unexplained, including why scenarioId is required. That is a major gap.

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

Purpose5/5

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

The description opens with a specific verb and resource: 'Snapshot the saved Canvas graph into a reusable template.' That distinguishes the creation action from sibling reads such as template_get or template_source, and 'reusable template' clarifies the artifact being produced.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete error-path alternative: on an unknown response, query template-source before retrying. However, it does not state the normal when-to-use conditions relative to siblings like from_template or append_template, nor any prerequisites beyond the implied saved canvas, so the guidance is useful but incomplete.

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