This server exhibits severe definition quality issues across nearly all dimensions. 14 of 21 tools (67%) have descriptions that are trivial forwarding statements ('Forward X to the live membrane') with zero actionable context. Only 7 tools expose input schemas; 14 tools have no visible schema at all. Tool names lack action verbs and are domain-specific jargon (corpus_bonds, critique_frame, umc_direct) that provide no semantic clarity to LLMs. No output schemas are documented. Error handling is absent. The server appears to be a thin HTTP proxy to an external 'membrane' service, with tool definitions inferred rather than explicitly registered in MCP format. This violates core MCP patterns for tool composition and LLM-friendly interface design.

• Rewrite all 14 trivial descriptions. For each tool, add: (1) What it does in one sentence, (2) When to use it vs similar tools, (3) What it returns. Target 50-200 chars per pattern:tool-description baseline. Example: 'verify_jordan_bond' → 'Verify if matrices A, B, K satisfy the Jordan bond constraint. Returns true/false and constraint violation details if applicable. Use after computing candidate matrices.'
• Add input schemas to all 14 tools missing them. Use JSON Schema with type, description, and enum/pattern constraints for each parameter. Example for umc_direct: {"type": "object", "properties": {"command": {"type": "string", "enum": ["start", "stop", "pause"], "description": "Execution command"}}, "required": ["command"]}
• Rename tools to start with action verbs. corpus_bonds → query_corpus_bonds or verify_corpus_bonds; critique_frame → evaluate_frame; umc_direct → execute_umc_command; ide_rebuild_mesh → rebuild_mesh. Follow verb_noun pattern from pattern:tool baseline.
• Document output schemas for all tools. Specify returned fields, types, and whether results are paginated. Example: 'Returns {"status": "success"|"error", "data": [...], "total_count": int, "next_cursor": string|null}'. This enables LLM tool chaining.
• Add error handling guidance to tool descriptions. Example: 'If membrane_health returns status=degraded, retry after 30s. If status=offline, ask user to check network. If status=unknown, contact support.' Follows pattern:recovery-guide and pattern:error-classification.