doc-bot
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_documentationB | Search project documentation and installed API references for patterns, examples, and usage details. Use early and often to stay aligned with current docs. |
| get_file_docsA | Get documentation that matches a file path or pattern using frontmatter filePatterns. Use when editing a specific file or directory. |
| read_specific_documentB | Read full documentation file content when you need complete context. |
| explore_apiB | Deep dive into any API, framework, or class from installed docsets. |
| create_or_update_ruleA | Create or update documentation as you discover new patterns, decisions, or changes. Use this to keep docs current for future agents. |
| refresh_documentationA | Reload all project documentation from disk when docs are updated externally. |
| get_document_indexB | List all available project documentation files with titles and metadata. |
| add_docsetB | Install a new documentation set (docset) for API reference. Supports both local .docset files and direct URLs. |
| remove_docsetA | Remove an installed documentation set. Use list_docsets first to see available docsets and their IDs. |
| list_docsetsA | List all installed documentation sets (docsets). Shows docset IDs, names, and installation details. |
| doc_botB | Documentation MCP guidance: suggests docs, search hints, and doc upkeep steps. Use frequently to stay aligned and capture new knowledge. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Documentation Store | All project documentation entries with titles, paths, and descriptions |
| Document Index | Titles and metadata for all documentation entries |
| Agent Guidance | Suggested guidance for using doc-bot documentation tools |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose: docset management (add, list, remove), documentation retrieval (search, read by file, read by ID, index, refresh), rule creation/update, API deep dive, and guidance. Overlaps are minimal and descriptions clarify boundaries.
Most tools use a consistent verb_noun snake_case pattern (e.g., add_docset, search_documentation). The tool 'doc_bot' breaks this pattern as a noun_noun, but it's a single outlier and still readable.
11 tools is well-scoped for a documentation MCP server. The set covers docset operations, documentation queries, rule management, and guidance without being overwhelming or too sparse.
The tool surface covers the full documentation lifecycle: install/remove docsets, create/update rules, search, read, index, and refresh. Missing operations like document deletion are not clearly needed based on the domain, so no obvious gaps.