Vocenya Docs

Each tool has a mostly distinct role: search_docs finds pages/endpoints, get_doc_page retrieves docs pages, list_endpoints lists API endpoints, and get_endpoint retrieves one endpoint in detail. There is minor overlap because get_doc_page can also fetch a resource's endpoint reference page (e.g. 'reference/leads'), which overlaps slightly with list_endpoints for the same resource.

All tool names use consistent snake_case with a clear verb_noun pattern: get_doc_page, get_endpoint, list_endpoints, search_docs. The convention is predictable and readable throughout.

Four tools are well-scoped for a documentation server: search, page retrieval, endpoint listing, and endpoint detail. Each tool earns its place, and there is no redundant or bloated surface.

The set covers the main read-only workflows for developer docs: searching, reading guide pages, listing API endpoints, and getting full endpoint details. A minor gap is the lack of an exhaustive way to list all documentation pages or guides, though search_docs largely compensates.