The UISpec MCP server has reasonable naming conventions and clear tool purposes, but suffers from incomplete parameter descriptions, missing output schema documentation, and lack of error handling guidance. 8 of 9 tools have descriptions, but parameter-level documentation is sparse. No visible schema documentation for outputs. Tool definitions are explicitly registered in pkg/mcp/tools.go using the mcp-go framework, but the implementation is cut off mid-definition, preventing full verification of all parameters.

• Document the output schema for all tools. For 'list_categories', specify: returns [{name: string, components: string[]}]. For 'validate_page', clarify: returns {valid: boolean, errors: [{line, message}], fixes?: [{original, suggested}]}.
• Add comprehensive parameter descriptions. E.g., 'names' in get_component_details: 'Array of component names to fetch (e.g. ["Button", "Dialog"]). Names are case-sensitive and must match catalog entries. Returns error if any name not found.'
• For 'validate_page', document which TSX errors are auto-fixable (e.g., typo in prop name, missing required prop) vs unrecoverable (e.g., invalid prop type). Guide the LLM: 'If auto_fix fails, call search_components to find correct component name or get_component_details to review props.'
• Add pagination support. Modify 'list_components' and 'search_components' to accept 'limit' (1-100, default 20) and 'offset' parameters. Return {results: [...], total: number, has_more: boolean} to enable iteration.
• For 'validate_page', add a 'dry_run' parameter (boolean, default true). When true, returns proposed fixes without applying. When false, applies fixes. This prevents accidental mutations and aligns with confirmation-request pattern.
• Clarify 'get_guidelines' behavior: does it return global guidelines only, or global + component-specific? Current description says 'global guidelines, or global + component-specific if a component name is given', split into two clearer parameters: 'include_global' (boolean, default true) and 'component' (optional string).

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry