Skip to main content
Glama

ai_modeling_canvas_template_delete

Destructive

Delete an explicitly selected Canvas template you own without affecting its source projects.

Instructions

Delete an explicitly selected template you own; source projects remain separate.

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": {
      "id": "<id>"
    },
    "name": "ai_modeling_canvas_template_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is known. The description adds genuine blast-radius context by noting source projects remain separate, but it never says the deletion is irreversible, what happens to canvases using the template, or what errors occur for non-owned ids.

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

Conciseness4/5

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

A single compact sentence with the resource and both constraints front-loaded and no wasted clauses. The semicolon construction is terse enough to read as slightly cryptic, which keeps it from a 5.

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

Completeness3/5

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

For a one-parameter destructive tool whose annotations already flag the mutation, the definition covers purpose, ownership, and blast radius. It is still thin on irreversibility and post-delete effects on canvases that reference the template, which an agent deciding whether to call it would want.

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 description must carry the load; it only implies that 'id' identifies an owned template. It adds no format, pattern, or source-vs-template id disambiguation, even though the schema itself constrains the value with a pattern and length bounds.

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 specific verb and resource ('Delete ... template') and adds two scoping qualifiers: the target must be an explicitly selected template and one the caller owns. This differentiates it from sibling template tools such as create/get/append, though it stops short of naming any of them.

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?

Usage is implied by the ownership restriction ('a template you own') and the deliberate-action framing ('explicitly selected'), but there is no statement of when to choose this over ai_modeling_canvas_template_source or how to remove a template's link from a canvas instead. Guidance is inferable rather than stated.

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