Skip to main content
Glama

list_canonical_templates

Read-onlyIdempotent

Retrieve canonical HTML/SVG component templates plus @krusch/toolkit and krusch_toolkit Lego starter bricks so agents can pick reusable building blocks for new components.

Instructions

List all available canonical HTML/SVG component templates and @krusch/toolkit & krusch_toolkit Lego starter bricks.

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": "list_canonical_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without description help. The description adds only what the listed items are (HTML/SVG templates and toolkit starter bricks), with no info on return format, whether the entries are names or identifiers, or how they feed the sibling getter.

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 front-loaded sentence with the verb first and no filler. The only cost is that the second half is stacked jargon ('@krusch/toolkit & krusch_toolkit Lego starter bricks') that reads as an enumeration rather than a clear content description.

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 no-param, no-output-schema enumeration tool with rich annotations, the description is minimally sufficient but leaves the return value entirely unexplained. An agent does not learn whether the list yields slugs, paths, or template bodies, nor that those results are the inputs to get_canonical_template, so the discovery→fetch workflow must be guessed.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to document. No parameter-level confusion is possible here.

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 ("List all available") and a concrete resource set: canonical HTML/SVG component templates plus @krusch/toolkit and krusch_toolkit Lego starter bricks. It is clearly a catalog/enumeration tool and implicitly contrasts with the singular get_canonical_template, though the 'Lego starter bricks' phrasing is domain jargon an agent may not fully parse.

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 only implied: an agent can infer this is the discovery step before get_canonical_template, but the description never says so explicitly and names no alternative. There are no prerequisites, exclusions, or when-not guidance, which is tolerable for a zero-parameter list tool but still a gap.

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