Dash 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_installed_docsetsA | List all installed documentation sets in Dash. An empty list is returned if the user has no docsets installed. Results are automatically truncated if they would exceed 25,000 tokens. |
| search_documentationA | |
| enable_docset_ftsB | |
| load_documentation_pageA | |
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
Each tool has a clearly distinct purpose with no overlap. enable_docset_fts configures search capabilities, list_installed_docsets enumerates available resources, search_documentation finds content, and load_documentation_page retrieves specific pages. The boundaries between these operations are well-defined and unambiguous.
All tool names follow a consistent verb_noun pattern with clear, descriptive action-object pairs. The naming convention is uniform throughout: enable_docset_fts, list_installed_docsets, load_documentation_page, and search_documentation all maintain the same structure and style.
Four tools is reasonable for a documentation search server, covering core operations of listing, searching, and viewing documentation. While this is a minimal but functional set, it could potentially benefit from additional utilities like docset management or search refinement tools, but the current count is appropriate for the basic scope.
The toolset provides complete coverage for the core documentation search workflow: discovering available docsets, enabling search features, searching across documentation, and loading specific pages. The only minor gap is the absence of docset installation/removal tools, but the server appears focused on search operations rather than full docset management.