DocsetMCP provides 3 well-named, read-only tools for documentation search. Tool names follow verb-noun convention (search_documentation, list_available_docsets, get_docset_languages). Descriptions are present and moderately detailed (120-150 chars). Input schemas are visible with proper types and descriptions for all parameters. However, output schemas are not documented in the visible code, parameter descriptions could be more detailed about constraints and expected formats, and there is no error handling guidance. The tools are simple, single-purpose, and appropriately scoped. No security concerns (read-only, no credentials). Overall quality is above-average for a STDIO server, but lacks the depth expected for 70+.
Get the list of supported languages for a specific docset
List all available docsets that can be searched
Search for documentation in a Dash docset
Output schemas not documented. Tool descriptions state what is returned, but the JSON structure of responses (field names, types, nested objects) is not formally declared in source code. LLMs cannot reliably extract data from undocumented response structures.
Parameter descriptions lack format/constraint details. The 'query' parameter for search_documentation has no guidance on length, special characters, or what constitutes a valid search term. The 'max_results' parameter lacks min/max bounds (e.g. 1-50). Descriptions should state: 'max_results: Integer, 1 - 50 (default 3). Limits returned entries; higher values may impact performance.'
No error handling guidance in tool descriptions. Descriptions do not mention what happens if a docset is not found, if a search returns zero results, or what the LLM should do if a language filter doesn't match. Error responses should include recovery suggestions (e.g. 'Docset not found. Available docsets: [list]').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-21 | F | 49 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 45 | - | v1 |
No pagination support visible. search_documentation accepts 'max_results' but no offset, cursor, or page parameter. For docsets with many matching entries, results could be truncated. Tool description should clarify: 'Returns top N results ordered by relevance. For more results, refine your query.'