This MCP server has severe definition quality issues. Only 2 tools are exposed, both with minimal schema documentation. The 'ping' tool lacks any visible input schema definition in the source code (PingController.php shows no explicit parameter registration). The 'api-catalog' tool returns an empty RFC 8288 linkset+json but has no documented output schema. Neither tool has parameter descriptions. Descriptions exist but are generic and do not follow LLM-optimized patterns (50-200 chars baseline). No error handling guidance, no input validation hints, and no composition support. Tool names lack action verbs ('api-catalog' is not verb_noun). The server appears to be a Craft CMS module wrapper around the stimmt/craft-mcp plugin, but tool definitions are not directly visible in the provided source, they are likely delegated to the plugin, making this a thin wrapper with inferred tool definitions.

• Add explicit JSON Schema input definitions for both tools. Document all parameters with type, description, and constraints (e.g., enums, min/max, regex patterns).
• Rename 'api-catalog' to 'describe_available_tools' or 'list_api_endpoints' to follow verb_noun convention and clarify intent.
• Expand tool descriptions to 50 - 200 characters, following LLM-optimized patterns: state WHAT the tool does, WHEN to use it, and what it returns. Example: 'ping: Returns Craft CMS system status including version, environment, plugins, and database driver. Use to verify server health before executing other tools.'
• Document output schemas formally. For 'ping', specify the exact fields returned (craft_version, environment, plugins[], queue_info, etc.) with types. For 'api-catalog', define the RFC 8288 linkset structure.
• Add error handling guidance. Document what errors each tool can return (e.g., 'ping' may fail if database is down) and what the LLM should do next (retry, ask user, or call a fallback tool).