@particle-academy/docs-mcp
OfficialServer 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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| docs_list_packagesA | List every @particle-academy/* (and other scanned) package that has docs available, with name, version, source (node_modules vs workspace), and file count. |
| docs_listA | List doc file paths. Each entry is the path you pass to docs_read. Optionally filter to one package. |
| docs_readA | Read the full markdown content of one doc file. Pass the package name and the path from docs_list. |
| docs_searchA | Search docs for a substring. Returns hits with package, path, line number, preview, and the section heading the hit lives under. |
| docs_refreshA | Re-scan the filesystem for docs. Call this after installing or updating a @particle-academy/* package mid-session. |
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 5 tools
Each tool has a distinct purpose: listing packages, listing file paths, reading content, refreshing the index, and searching. No overlap or ambiguity.
All tools follow a consistent 'docs_' prefix with snake_case verb_noun naming, making it easy to predict tool behavior.
5 tools is a well-scoped set for a documentation server, covering essential operations without bloat or deficiency.
The tool surface covers all necessary operations for documentation: listing packages and files, reading, searching, and refreshing. No obvious gaps for the intended domain.