CRITICAL: No tool definitions are visible in the provided source code. The validate.mjs script references 7 tool names (wet_benchmark_value, wet_search_events, wet_screen_markets, wet_event_markets, wet_cross_venue, wet_event_headlines, wet_resolve) but contains NO schema definitions, parameter descriptions, or output documentation. The script is a validation harness, not a tool registry. Without access to the actual MCP server implementation (likely at https://www.worldeventtrading.com/api/mcp), tool definitions cannot be assessed. Per hard scoring rules: if tool definitions are inferred rather than directly visible, cap per-tool scores at 50; if schemas are not visible, schema score must be 0; if descriptions are not visible, description score must be 0. All 7 tools score 0 overall.

• Provide the complete MCP server implementation (handler code, tool registration, schema definitions) for evaluation. The validate.mjs script is a test harness, not a tool definition source.
• For each tool, write a 50 - 200 character description explaining WHAT it does, WHEN to use it, and what it returns. Example: 'wet_search_events: Search for prediction market events by keyword, date range, or category. Returns event ID, title, description, and current odds.'
• Define explicit JSON Schema for each tool's input parameters with types, descriptions, enums (for constrained values), and min/max bounds. Example: { "type": "object", "properties": { "query": { "type": "string", "description": "Search term (2-100 chars)" }, "limit": { "type": "integer", "minimum": 1, "maximum": 100, "default": 20 } }, "required": ["query"] }
• Document output schemas for each tool. Specify which fields are returned, their types, and what they represent. Include pagination info (total_count, next_cursor) if results can be large.
• Add error handling guidance to tool descriptions. Example: 'If event not found, returns error code 404 with available event categories. Retry with search_events() to discover valid event IDs.'