This is a schema validation/linting tool, not a production MCP server. The four demo tools are intentionally flawed examples for testing the checker. Tool descriptions are minimal (10-50 chars), far below the 194-char baseline. No parameter descriptions exist. Schemas are present but deliberately contain violations (root anyOf, open additionalProperties). The server is not designed for agent use, it's a reference implementation for a JSON Schema compliance checker.

• Expand tool descriptions to 100-200 characters explaining what each tool does, when to use it, and what it returns. Example: 'search: Find items by keyword. Accepts a search query (1-200 chars) and optional result limit (1-100). Returns matching items with IDs and metadata.'
• Add descriptions to all parameters. For 'q': 'Search query string (1-200 characters, required)'. For 'limit': 'Maximum results to return (1-100, default 20)'. For 'url'/'id': 'Either a URL or resource ID (one required, not both)'.
• Document output schemas for each tool. Example: 'Returns {results: [{id, title, score}], total_count, next_cursor}'.
• Remove root-level combinators (anyOf, oneOf, allOf) from fetch_either. Restructure as a single object with both url and id optional, or split into separate tools (fetch_by_url, fetch_by_id).
• Restrict additionalProperties to false on all objects unless dynamic fields are genuinely required. For upsert, either enumerate allowed meta fields or document why open schemas are necessary.