Tambo Docs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_docsC | Fetch documentation content from docs.tambo.co |
| search_docsC | Search for documentation pages containing specific terms |
| list_sectionsB | Dynamically discover and list all available documentation sections |
| discover_docsB | Crawl the main docs page to discover all available documentation paths |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tools have mostly distinct purposes: discover_docs crawls the main page for paths, fetch_docs retrieves content, list_sections lists sections, and search_docs searches for terms. However, discover_docs and list_sections could be slightly confused as both involve discovering documentation structure, though their descriptions clarify one is for paths and the other for sections.
All tool names follow a consistent verb_noun pattern with snake_case, such as discover_docs, fetch_docs, list_sections, and search_docs. This uniformity makes the set predictable and easy to understand.
With 4 tools, the count is reasonable for a documentation server, covering core operations like discovery, fetching, listing, and searching. It might be slightly thin if advanced features like filtering or updating are needed, but it's well-scoped for basic documentation access.
The tools cover key documentation access operations: discovery, fetching, listing, and searching. However, there are notable gaps, such as no tools for creating, updating, or deleting documentation, which might be expected in a full documentation management system, limiting the surface to read-only access.