MCP server for searching and retrieving PyTorch documentation
Single tool with acceptable naming (get_documentation) but significant gaps in schema completeness, parameter descriptions, and output documentation. The tool description is adequate (108 chars, within 10-1024 range) but parameter descriptions are minimal. No output schema documented. Error handling is basic (ValueError for unsupported library, generic timeout/no-results strings). The implementation exposes external API dependency (SERPER_API_KEY) via environment variable (good), but lacks structured output and pagination guidance.
Search the latest documentation of any provided library using the query. Currently only supports PyTorch.
Output schema not documented. Tool returns unstructured text concatenation from multiple URLs with no field definitions, making it impossible for LLMs to parse or chain results.
Parameter descriptions are minimal (e.g., 'The query to search for' lacks format/length constraints). No guidance on expected query format, length limits, or examples of valid queries.
Library parameter should be an enum (currently only 'pytorch' supported) rather than free-form string. This prevents LLM hallucination of unsupported libraries.
Error messages are generic and non-actionable. 'No search results for the query X' and 'Timeout error' provide no recovery guidance. Should suggest fallback queries or alternative approaches.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 46 | 2026-07-28+ | v2 |
No pagination or result limiting documented. Tool concatenates all results from multiple URLs into a single unstructured text block, risking context window exhaustion and token waste.