Skip to main content
Glama
krusch-frontend-mcp

krusch-frontend-mcp

by kruschdev

list_canonical_templates

Read-onlyIdempotent

Lists available canonical HTML and SVG design templates plus toolkit starter bricks for homelab projects, helping you find a base layout before building.

Instructions

Lists all available canonical HTML/SVG design templates and @krusch/toolkit & krusch_toolkit Lego starter bricks for homelab projects.

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.1.1

TDQS

A3.6/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 by structured data. The description adds only scope information — which template families are included — and says nothing about return shape, ordering, or whether the listing is static versus dynamic. With annotations carrying the behavioral burden, this is adequate but not additive.

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 and subject first — no filler, no restatement of the title. The trailing qualifier "for homelab projects" and the toolkit naming add domain color but risk being noise if an agent doesn't know what a krusch_toolkit brick is.

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 zero-parameter, read-only, closed-world listing tool with full annotation coverage, the description states enough to invoke it correctly and understand what comes back categorically. The remaining gap is what an agent should do with the results (e.g., feed an identifier into get_canonical_template), which would make it fully complete.

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 and the schema is an empty object, so there is no parameter semantics to explain; baseline is 4. The description does not need to compensate for anything here, though it could have noted that no filtering arguments exist so the agent doesn't look for them.

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 opens with a specific verb ("Lists") and enumerates the resources returned: canonical HTML/SVG design templates plus @krusch/toolkit and krusch_toolkit starter bricks. An agent can tell this is a catalog-enumeration tool, and "all available" implicitly contrasts with the singular get_canonical_template sibling, though it never names it. The jargon ("Lego starter bricks") is opaque to an outside reader and slightly blurs what is actually being listed.

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 by the word "all available" — an agent can infer this is the discovery/listing entry point, but nothing states when to use it versus get_canonical_template or the other frontend tools. There are no explicit exclusions, prerequisites, or follow-up instructions (e.g., "then pass an id to get_canonical_template").

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