This MCP server has severe definition quality issues. Both tools lack proper parameter descriptions, have empty input schemas with no type information, and lack actionable error handling guidance. Tool 1 (clade_list_skills) is read-only and relatively safe but still poorly documented. Tool 2 (clade_<skill_name>) is dynamically generated with a generic description that does not specify which skills are available, what parameters each skill accepts, or what the expected output format is. The dynamic tool generation pattern is inferred rather than directly visible in the schema definitions provided. No tool descriptions explain WHEN to use the tool, WHAT it returns, or HOW to recover from failures. Parameter schemas are empty objects, no type, minimum, maximum, enum, or format constraints. This violates multiple critical patterns from the rubric.

• Define explicit input schemas for both tools. For clade_list_skills, add parameters like `filter_by_category` (enum or string) or `include_hidden_skills` (boolean). For clade_<skill_name>, replace the generic placeholder with actual skill names (clade_commit, clade_test, etc.) and define parameters specific to each skill's actual API.
• Expand clade_list_skills description to 150 - 250 characters: 'Returns a list of all available Clade skills with their names, descriptions, required parameters, and usage examples. Call this first to discover available automation tools. Each skill object contains: name (string), description (string), parameters (object with type and description for each param), category (string).'
• For clade_<skill_name> tools (once individualized), add descriptions that specify: (1) What the skill does (verb phrase), (2) When to use it vs other skills, (3) Required parameters with type and example, (4) What it returns, (5) Possible errors and recovery steps. Example: 'Executes the commit skill to create a Git commit with specified message and file list. Provide a commit_message (string, required) and files (array of strings, paths to stage). Returns {commit_hash, branch, files_changed}. If files not found, returns {error: "File not found", details: {path, suggestion}}.'
• Add parameter descriptions even for dynamic tools. Use the skill list response to populate parameter metadata dynamically, ensuring the MCP server always reflects the current Clade skill API.
• Add error recovery guidance to clade_<skill_name>: 'If a skill fails, call clade_list_skills to verify the skill exists and check parameter requirements. Common errors: missing_dependency (install it and retry), permission_denied (verify you have write access), timeout (the skill may be long-running, increase timeout or break into smaller steps).'