Related Servers

Each tool is anchored to a distinct retrieval mode: index browsing (list_docs), keyword search (search_docs), single-page fetch (read_doc), batch fetch (read_docs_batch), code-only extraction (get_code_examples), cross-SDK topic matching (find_across_sdks), recency (list_recent_updates), and curated product docs (get_product_guide). The main soft spots are search_docs vs find_across_sdks (keyword vs per-source topic) and get_product_guide vs read_doc, which overlap but are disambiguated by the verbose descriptions. The sheer density of each description helps precision but makes boundaries slower to grasp.

Uniform snake_case verb_noun pattern across all eight tools: read_doc, read_docs_batch, list_docs, list_recent_updates, get_code_examples, get_product_guide, search_docs, find_across_sdks. The verbs (read/list/get/search/find) map predictably to retrieval semantics, and singular/plural (read_doc vs read_docs_batch) correctly signals cardinality.

Eight tools is well within the sweet spot for a documentation server, and each earns its place: browsing, searching, single read, batch read, code extraction, cross-platform comparison, recency, and product docs. No redundant or filler tools are present.

The surface covers the full discovery-to-retrieval lifecycle (TOC → search → read → batch → code snippets) plus niche needs like cross-SDK comparison and recent changes, with pagination/continuation handled everywhere. Minor gaps: no explicit tool to enumerate available sources/sections metadata beyond list_docs modes, and no dedicated API-reference or schema lookup, though find_across_sdks partly covers REST API discovery.