Skip to main content
Glama
Sign In
web-ui-component-spec-mcp

web-ui-component-spec-mcp

by gcsebas99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

validate_component_checklist

Compare implemented component features against specs and test scenarios to get a coverage report of what's covered and missing. Use to QA a component before marking it done.

Instructions

Compare an implementation against the spec's Main Features and Test Scenarios. Returns a coverage report showing what's covered, what's missing, and an overall status. Use this to QA a component before marking it done.

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": {
      "component": "<component>",
      "implemented_features": "<implemented_features>"
    },
    "name": "validate_component_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
componentYesComponent name or id.
implemented_featuresYesList of strings describing what has been implemented. Be specific: e.g. ['closes on Escape key', 'traps focus within modal', 'has aria-modal attribute', 'backdrop click dismisses modal']
check_testsNoAlso check against Test Scenarios (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description must cover behavioral aspects. It states the tool returns a coverage report showing covered, missing, and status, but does not disclose potential side effects, error conditions (e.g., if component doesn't exist), or performance implications. This is adequate but lacks full transparency.

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

Conciseness5/5

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

The description is extremely concise with only two sentences. The first sentence states the action and output, the second gives usage guidance. No unnecessary words or repetition.

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?

Given the tool has 3 parameters (2 required), no nested objects, no enums, and no output schema, the description covers the essential aspects: purpose, usage, and basic behavior. It lacks details on output structure (e.g., report format) but is sufficient for an agent to understand the tool.

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?

Schema description coverage is 100%, so baseline is 3. The description adds value by explaining the comparison targets ('Main Features and Test Scenarios'), which provides context for the 'implemented_features' and 'check_tests' parameters beyond their schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: comparing an implementation against spec's Main Features and Test Scenarios, returning a coverage report. It uses specific verbs and resources, distinguishing it from sibling tools like 'get_component_spec' or 'get_component_tests' which retrieve rather than compare.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance: 'Use this to QA a component before marking it done.' This sets clear context for when the tool should be invoked. However, it does not mention when not to use it or suggest alternative tools, though the context is sufficiently clear given sibling names.

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

Deploy Server

Other Tools