Server has 4 tools with explicit schemas and descriptions. Naming follows verb_noun pattern (grok_login, grok_auth_callback, x_search, web_search). Descriptions are present but brief (34-194 chars). All tools have input schemas with type definitions. However, output schemas are not documented, responses are JSON strings with 'ok', 'code', 'error', 'text', 'citations', 'model' fields, but LLMs cannot see this structure. Error handling returns structured error objects (code + message) which is good, but recovery guidance is minimal. Parameters lack detailed constraints (e.g., date format validation happens server-side but not declared in schema descriptions). No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Overall: functional but below production baseline.

• Document output schemas explicitly. Define the response structure for each tool (e.g., grok_login returns {ok: boolean, authorize_url?: string, expires_in_sec?: number, message?: string, code?: string, error?: string}). This enables LLMs to extract fields reliably.
• Add format constraints to parameter descriptions. Change 'Optional start date in YYYY-MM-DD format' to 'ISO 8601 date string (YYYY-MM-DD). Example: 2024-01-15. Invalid format returns BAD_REQUEST error.' Use Zod's .describe() to embed these in schema.
• Add tool annotations via MCP SDK. Mark grok_login, grok_auth_callback, x_search, web_search with readOnlyHint: true to signal they are safe to cache and retry.
• Enhance error messages with recovery hints. Change 'LOGIN_EXPIRED' error to include 'Call grok_login to start a new session.' Change 'BAD_REQUEST' errors to suggest valid values (e.g., 'allowed_domains allows at most 5 entries; you passed 7. Remove 2 and retry.').
• Implement a local callback server or provide a helper to extract the code from the redirect URL. The current manual copy-paste flow is error-prone. Consider wrapping the OAuth flow in a single tool that handles the full redirect cycle.