The server exposes 3 tools with partial schema definitions and basic descriptions. All three tools have explicit registrations in app/routes.py with names, descriptions, and parameter schemas visible. However, there are significant gaps: (1) Parameter descriptions are minimal and lack actionable constraints (e.g., no limits on query length for brave_search, no format hints for openai_chat prompt). (2) Output schemas are not documented, callers cannot determine the structure of results. (3) Error handling is minimal; the invoke endpoint returns generic 404/500 responses without recovery guidance. (4) No parameter validation constraints (enums, ranges, patterns) are declared in the schemas. (5) Tool names lack clear action verbs, 'openai_chat' is somewhat ambiguous (send_prompt? query_llm?), 'wikipedia_person' conflates lookup+summarization. The server demonstrates basic MCP tooling but falls short of production-grade quality.

• Document the output schema for each tool. For openai_chat, specify: 'Returns a string containing the LLM response.' For wikipedia_person, specify: 'Returns {extract: string, title: string, url: string} or error message if not found.' For brave_search, specify: 'Returns {results: [{title: string, url: string, snippet: string}]}.'
• Add parameter constraints to descriptions. For openai_chat.prompt, add: '(1-4000 characters, UTF-8 text).' For wikipedia_person.name, add: '(Full or partial name; diacritics handled; returns 404 if no page found).' For brave_search.query, add: '(1-200 chars; supports boolean operators: AND, OR, NOT)' and for count, add: '(1-20; default 5).'
• Improve error messages in /invoke to guide recovery. Replace generic 500 with context: 'Error invoking brave_search: BRAVE_API_KEY not set. Ensure the environment variable is configured.' For Wikipedia 404, surface: 'Person not found on Wikipedia. Try a simpler name or check spelling.'
• Rename tools for clarity. 'openai_chat' → 'query_openai' or 'send_prompt'. 'wikipedia_person' → 'search_wikipedia_person'. 'brave_search' → 'search_web' (more portable if switching search providers).
• Add permission/scope declarations. Document which tools require API keys or special permissions: openai_chat (OPENAI_API_KEY), brave_search (BRAVE_API_KEY). Include scope hints: e.g., 'read:web-search (Brave Search API).'
• Implement pagination for brave_search. Accept offset/cursor parameter. Return next_cursor if more results available. Cap max count at 20 and document the limit in the tool description.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry