Skip to main content
Glama
krusch-frontend-mcp

krusch-frontend-mcp

by kruschdev

query_design_rules

Read-onlyIdempotent

Retrieve relevant design guidelines, CSS architecture rules, and accessibility standards using semantic search with optional paradigm filters for frontend implementation.

Instructions

Semantic RAG search over specific design guidelines, CSS architecture, and accessibility standards.

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": {
      "queryStr": "<queryStr>"
    },
    "name": "query_design_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
paradigmNoOptional aesthetic paradigm to filter by (e.g. 'universal', 'refactoring-ui', 'vercel', 'apple-hig', 'material-design')
queryStrYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds that retrieval is semantic rather than keyword-based, which is genuinely useful behavioral context, but says nothing about result count, ranking, or whether an empty paradigm means unfiltered search.

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 no filler; the search mechanism and the content scope come first. It is efficient, though it is arguably too terse to earn full marks on structure.

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 2-parameter read-only retrieval tool with no output schema, the definition covers the essentials but omits how the two parameters interact (does paradigm constrain queryStr?) and what kind of payload comes back. Adequate as a minimum viable description, not complete.

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 coverage is only 50%: 'paradigm' is well documented in the schema with examples, but 'queryStr' has no schema description at all. The description does not compensate by explaining what a good query string looks like or how broad/narrow it should be, leaving the required parameter under-specified in both places.

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 retrieval mechanism ('Semantic RAG search') and concrete content domains (design guidelines, CSS architecture, accessibility standards), which distinguishes it from the generation-oriented siblings like generate_component_styles or css_to_tailwind. It does not explicitly name a sibling it supersedes, so it stops short of a 5.

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?

There is no statement of when to call this versus the many generation tools, no prerequisites, and no note on when to prefer a direct template lookup (get_canonical_template) over a semantic query. The agent must infer usage from the domain words alone.

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