Skip to main content
Glama

ai_modeling_canvas_template_source

Read-only

Finds the template authored from a specified Canvas source project and returns null when no template exists, letting agents verify template availability before reuse.

Instructions

Find the template authored from a source Canvas project; template is null when none exists.

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>"
    },
    "name": "ai_modeling_canvas_template_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceProjectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish read-only, non-destructive, and open-world behavior. The description adds useful behavioral context by stating that the template is null when none exists, but it does not cover permissions, error behavior, or anything beyond that null-result case.

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?

The definition is a single front-loaded sentence with no wasted wording. The key lookup condition and null-result behavior are both stated efficiently.

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

Completeness4/5

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

For a simple one-parameter lookup with annotations covering safety, the description is largely complete: it identifies the lookup basis and states the null case. It could do slightly more about the returned template or how to source the project ID, but no major gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema only enforces format constraints and does not explain the parameter. The description compensates partially by clarifying that sourceProjectId refers to the source Canvas project, but it does not explain where to obtain the ID or its expected relationship to other project identifiers.

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?

The description states a specific verb and resource: finding the template authored from a source Canvas project. It distinguishes this lookup from a generic template_get by tying it to a source project, though it does not explicitly name alternatives.

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?

The mention of a source Canvas project implies the tool is used when a sourceProjectId is available and the associated template is needed. It does not state when not to use it or name a sibling alternative for other lookup cases.

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