Uni-CLI MCP Server exposes 4 tools with partial schema coverage. Tool naming is verb-based and descriptive (unicli_run, unicli_list, unicli_search, unicli_explore), following pattern:tool conventions. However, critical gaps exist: (1) unicli_explore description is truncated mid-sentence ('Auto-discover API endpoints for any URL. (2) Input schemas vary in completeness: unicli_run and unicli_list have well-formed JSON Schema with typed properties and required fields; unicli_search has extremely complex multi-level enum constraints (operator, target_surface, effect, max_interaction_impact, platform); unicli_explore has NO visible schema in source. (3) Parameter descriptions are present and specific (e.g., 'Site name (e.g. hackernews, github, bilibili)' for site param, 'Opaque next_cursor from the previous page' for cursor), but several lack constraints: unicli_run's 'args' param is additionalProperties without format guidance. (4) Output schemas are completely undocumented across all 4 tools, no description of what fields agents should expect in responses, breaking the pattern:tool-chain requirement. (5) Error handling is not visible in source, no recovery guidance, categorization, or actionable error messages. Baseline: avg tool description 194 chars; Uni-CLI tools range 40 - 200 chars but one is incomplete. Baseline: 100% A+ tools document return types; Uni-CLI documents 0%.

• Add complete output schema documentation for all 4 tools. Document return object structure, field types, and example values. E.g., for unicli_run: {"success": boolean, "output": object, "execution_time_ms": number, "warnings": string[]}. This enables LLM chaining and field extraction.
• Complete unicli_explore description: replace 'generates YAML ada' with a full, coherent description. E.g., 'Auto-discover API endpoints for any URL by navigating the page, capturing network requests, and generating YAML specifications. Returns discovered endpoints, methods, and parameter schemas.'
• Add input schema for unicli_explore. Include parameters for URL, discovery timeout, filters (e.g., method, path patterns), and output format options.
• Replace example values with formal constraints. For unicli_run args param, document expected structure as JSON Schema example: {"type": "object", "properties": {"query": {"type": "string"}, "limit": {"type": "integer", "minimum": 1, "maximum": 100}}}. Or link to Uni-CLI command documentation.
• Add per-tool error handling section. Document likely error codes (e.g., 'command_not_found', 'invalid_site', 'api_rate_limit') and recovery paths. E.g., 'If site not found: call unicli_list with no filters to discover available sites.'
• Split unicli_search into 2 - 3 focused tools if the 5 enum filters are mutually exclusive use cases. E.g., search_by_intent (query, limit) + search_by_effect (effect filter) + search_by_platform (platform filter). Reduces cognitive load and improves LLM precision.