Skip to main content
Glama

ai_modeling_canvas_from_template

Creates a Canvas from a chosen template and sets an optional name, helping agents start structured Canvas projects without manual setup.

Instructions

Create a Canvas from a template.

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": {
      "templateId": "<templateId>"
    },
    "name": "ai_modeling_canvas_from_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
templateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.1/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 covered. The description adds nothing beyond that: it does not say whether the new canvas is returned, whether the template is copied or linked, or what permissions are needed.

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 no filler, which is structurally clean. However, the brevity comes from under-specification rather than disciplined editing, so it earns no more than an adequate score.

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?

This is a mutating, open-world tool with no output schema and zero parameter coverage, so the description is the only place to explain effects and return behavior. It supplies none of that, leaving an agent unable to predict what it gets back or what the call changes.

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 carry parameter meaning and does not. 'From a template' weakly implies templateId, but the optional name parameter, the id pattern constraints, and the relationship between the two are entirely undocumented outside the raw schema.

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

Purpose2/5

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

The sentence 'Create a Canvas from a template' essentially restates the tool name ai_modeling_canvas_from_template, adding only the implicit notion of creation. It does not distinguish this from siblings like ai_modeling_canvas_create or ai_modeling_canvas_append_template, so an agent cannot tell which creation path applies without inspecting other definitions.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. Given that sibling tools include canvas_create and canvas_append_template, the absence of any routing signal leaves selection to guesswork.

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