ClawQL MCP exposes only 2 tools ('cache' and 'audit') with minimal documentation. Both tools lack visible input schemas, parameter definitions, and detailed descriptions. Tool descriptions are generic placeholders ('ClawQL Core cache tool', 'ClawQL Core audit tool') under 30 characters, far below the 194-char baseline for production tools. No evidence of parameter documentation, output schemas, or error handling guidance. Source code provided (Makefile, mcp.json) shows deployment configuration but no tool implementation details. Tool definitions appear inferred rather than explicitly registered with schemas.

• Add explicit input schemas for both tools with typed parameters (e.g., {"type": "object", "properties": {...}, "required": [...]}).
• Expand tool descriptions to 100-200 characters explaining purpose, use case, and return value. Example: 'cache' → 'Retrieve or manage ClawQL cache state. Returns cache hit/miss stats, memory usage, and eviction policy. Use to diagnose performance issues.'
• Rename tools with action verbs: 'cache' → 'get_cache_stats' or 'clear_cache'; 'audit' → 'list_audit_logs' or 'search_audit_events'.
• Document all parameters with type, description, constraints, and examples. E.g., 'cache_key (string, required): The cache entry identifier. Pattern: [a-zA-Z0-9_-]{1,255}.'
• Add output schema documentation showing field names, types, and sample values. Include pagination support (limit, offset, total_count) if results can be large.

Inferred effective spec: 2026-07-28+.

• Current-spec patterns present: Streamable HTTP