Skip to main content
Glama

ai_modeling_canvas_templates

Read-only

List Canvas templates and their reusable graphs to locate reusable modeling workflows, filtered by placement and scenario.

Instructions

List Canvas templates and their reusable graphs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ai_modeling_canvas_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNo
pageSizeNo
placementNo
scenarioIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.4/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 safety is covered. The description adds nothing beyond naming the resource: it says nothing about pagination behavior, default page size, whether results span home and project placements, or how scenarioId narrows results.

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?

One short, front-loaded sentence with no filler, which is good. But the brevity comes from under-specification rather than precision — the single clause about "reusable graphs" is not actionable.

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?

A paginated, filterable list tool with four undocumented parameters and no output schema needs the description to explain pagination and filter semantics. None of that is present, leaving the agent to guess how to page and scope results.

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% across four parameters, so the description carries the full burden and largely fails. offset, pageSize, placement, and scenarioId are mentioned nowhere; an agent cannot infer that placement filters home vs project templates or that scenarioId scopes by scenario.

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?

States a verb and resource ("List Canvas templates") plus a vague extra ("their reusable graphs"). It does not distinguish this from sibling template-listing tools such as ai_modeling_image_templates or ai_modeling_share_templates, so an agent cannot tell which template type it needs.

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?

No when-to-use, when-not-to-use, or alternative mentioned. Nothing tells the agent whether to call this directly or to use ai_modeling_canvas_from_template / ai_modeling_canvas_append_template once a template is chosen.

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