Skip to main content
Glama

get_canonical_template

Read-onlyIdempotent

Fetch a canonical starter template by ID to scaffold consistent HTML/SVG, Vercel, or Lego components and apps, reducing boilerplate setup.

Instructions

Retrieve a canonical HTML/SVG, Vercel, or @krusch/toolkit & krusch_toolkit Lego starter template (article-shell, site-header, footer-deadbolt, cyber-grid, deadbolt-svg, nav-back, lego-node-api, lego-mcp-server, lego-sse-route, lego-react-shell, lego-fastapi-app, lego-cloudflare-worker, lego-webhook-route, lego-vercel-nextjs-shell, lego-vercel-edge-sse, lego-vercel-json).

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": {
      "template_id": "<template_id>"
    },
    "name": "get_canonical_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
template_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds only that the returned content is a template of a particular family (HTML/SVG, Vercel, Lego) and says nothing about the return shape, size, or whether content is returned raw vs wrapped.

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

Conciseness2/5

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

A single run-on sentence whose bulk is a 16-item id list duplicating the input schema exactly, plus redundant branding ('@krusch/toolkit & krusch_toolkit'). The core action is front-loaded but buried under unnecessary enumeration.

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 read tool with rich annotations and a fully enumerated schema, this is minimally adequate: an agent knows what to call and with which id. It lacks any sense of what the returned template looks like or how large it is, which is the main residual gap.

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 carries the burden, but it merely restates the enum values verbatim without explaining what any template contains or how they differ (e.g., what article-shell vs cyber-grid yields). An agent gains no meaning beyond the self-descriptive id strings.

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 (Retrieve) and resource (a canonical template) and names the template families (HTML/SVG, Vercel, Lego starter). The purpose is legible, but the long parenthetical id dump dilutes it and there is no differentiation from the sibling list_canonical_templates.

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 guidance is given. An agent must infer from the sibling name list_canonical_templates that this tool fetches one template by id rather than enumerating them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.