Single tool with reasonable naming but significant gaps in description quality, parameter documentation, and output schema definition. Tool name 'minima-query' is action-oriented (acceptable) but description is brief and lacks context on when/how to use it. Input schema is present and typed, but parameter description is minimal (10 chars: 'context to find'). No documented output schema, callers cannot predict response structure. Error handling exists but lacks recovery guidance. Prompts feature is listed but implementation is incomplete (get_prompt handler has syntax error 'Mcp' without definition). Overall resembles a D+ grade: basic functionality present but multiple production-readiness gaps.

• Expand tool description from current ~40 chars to 150 - 250 chars: 'Search local documents (PDF, CSV, DOCX, MD, TXT) for a specific context or phrase. Returns matching excerpts with file references. Use when you need to find information in the user's uploaded files.' This tells LLMs WHAT, WHEN, and WHAT-IT-RETURNS.
• Rewrite 'text' parameter description to include format guidance: 'Search query or context phrase to find in documents. Can be a natural-language question (e.g., "Where is the office location?") or a keyword list. Minimum 1 character, maximum 500 characters.'
• Add explicit output schema documentation in server.py docstring or tool definition: return type is list[TextContent]; clarify what the text field contains (matching excerpts, file paths, page numbers?). Example: 'Returns a single TextContent with field text containing matching document excerpts and file references in format: "[filename] line 42: excerpt..."'
• Improve error messages to guide LLM recovery: instead of bare McpError, return 'No matches found in documents. Try a simpler search term or check file upload status with minima-query("test").' For internal errors, include: 'Search service temporarily unavailable; retry in 5 seconds or check server logs.'
• Fix get_prompt syntax error (undefined 'Mcp') and clarify relationship between minima-query tool and minima-query prompt. Currently both exist with same name but different interfaces, consider renaming or consolidating.
• Document whether the tool is idempotent (safe to retry) and whether it modifies state. Currently read-only, so mark with idempotentHint annotation if MCP spec version supports it.

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

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