Skip to main content
Glama
krusch-frontend-mcp

krusch-frontend-mcp

by kruschdev

get_canonical_template

Read-onlyIdempotent

Retrieve the authoritative bit-for-bit HTML/SVG component template or toolkit Lego starter brick by key to ensure deterministic frontend source.

Instructions

Returns the authoritative bit-for-bit HTML/SVG component template or @krusch/toolkit & krusch_toolkit Lego starter brick for krusch.dev and homelab projects.

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

Input Schema

NameRequiredDescriptionDefault
templateKeyYesThe canonical template or Lego starter brick key to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.4/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 safety is covered structurally. The description adds a fidelity guarantee ("authoritative bit-for-bit") which tells the agent not to reformat or paraphrase the result, but it says nothing about payload size, pagination, or failure behavior for invalid keys.

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?

One front-loaded sentence with no filler, leading with the verb and the guarantee before the brand-specific jargon. The stacked identifiers ("@krusch/toolkit & krusch_toolkit Lego starter brick") are dense but each carries real meaning.

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 full enum coverage and rich annotations, most of the burden is already met by structured fields. The gap is the return shape: with no output schema, the description never states whether the caller receives a raw source string, an object with metadata, or multiple files, which matters for a code-retrieval tool.

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 coverage is 100% and the single `templateKey` parameter carries a full enum plus its own description, so the baseline is 3. The description's contribution is modest: it distinguishes two families within the enum (HTML/SVG components vs. Lego starter bricks), which marginally aids key selection.

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 uses a concrete verb ("Returns") plus a specific resource ("authoritative bit-for-bit HTML/SVG component template or ... Lego starter brick"), and it scopes the content to krusch.dev and homelab projects. It stops short of naming `list_canonical_templates` as the discovery counterpart, so the agent must infer that this tool fetches content while the sibling enumerates keys.

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: the word "authoritative bit-for-bit" hints the tool should be used when exact source fidelity matters rather than reconstructing markup. There is no explicit statement of when to prefer it over `list_canonical_templates` or how to obtain a valid templateKey before calling.

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