Offline MCP server for Apple Developer Documentation, reading directly from a Dash-format Apple_API_Reference.docset
Four well-named tools with clear, detailed descriptions and comprehensive input schemas. All tools follow verb_noun naming (search_, get_, list_). Descriptions are 150 - 350 chars, exceeding the 10 - 1024 baseline. Parameters include type constraints (enums for language), ranges (limit 1 - 100), and detailed guidance. However, output schemas are not formally documented, responses are free-form markdown strings rather than structured objects. Error handling is present but generic ('No matches', 'Not found'). No tool annotations (readOnlyHint, idempotentHint) despite all being read-only operations. Missing pagination support for search results.
Return the full Apple documentation page as markdown — declaration, parameters, discussion, topics, see also. Inline cross-references in the returned markdown are canonical paths (e.g. `[modalPresentationStyle](/documentation/uikit/uiviewcontroller/modalpresentationstyle)`). Pass any of them back into this tool to navigate.
List all Apple frameworks present in the docset.
List the symbol kinds available in the docset, with counts.
Search the Apple docset. Returns a list of matching symbols with their kind, framework, and canonical path. Pass any returned path to `get_apple_doc` for full content.
Output schemas not documented. All tools return free-form markdown strings instead of structured objects. LLMs cannot reliably extract fields for downstream tool calls or plan multi-step workflows.
No tool annotations despite all tools being read-only. Adding readOnlyHint=true to all four tools would signal to agents that these are safe, non-destructive operations.
search_apple_docs returns up to 25 results (default) but no pagination support. Large result sets are returned as unstructured markdown lists, risking context window exhaustion and degraded LLM reasoning.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2026-07-28+ | v2 |
Error messages are generic ('No matches', 'Not found') and do not guide recovery. Missing actionable guidance like 'Try search_apple_docs() with a broader query' or 'Check framework name spelling'.
list_types has empty input schema (no parameters). Description is brief (47 chars) and does not explain what 'types' means (symbol kinds: Class, Struct, Method, etc.) or when to call it.