Atlas-Docs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
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 |
|---|---|
| list_docsA | Lists all available documentation libraries and frameworks. Use this as your first step to discover available documentation sets. Returns name, description and source url for each documentation set. Required before using other documentation tools since you need the docName. |
| search_docsA | Searches a documentation set for specific content. Use this to find pages containing particular keywords, concepts, or topics. Returns matching pages ranked by relevance with their paths and descriptions. Follow up with get_docs_page to get full content. |
| get_docs_indexA | Retrieves a condensed, LLM-friendly index of the pages in a documentation set. Use this for initial exploration to understand what's covered and identify relevant pages. Returns a markdown page with a list of available pages. Follow up with get_docs_page to get full content. |
| get_docs_pageA | Retrieves a specific documentation page's content using its relative path. Use this to get detailed information about a known topic, after identifying the relevant page through get_docs_index or search_docs. Returns the complete content of a single documentation page. |
| get_docs_fullA | Retrieves the complete documentation content in a single consolidated file. Use this when you need comprehensive knowledge or need to analyze the full documentation context. Returns a large volume of text - consider using get_docs_page or search_docs for targeted information. |
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 clearly distinct purpose with no overlap: list_docs discovers documentation sets, get_docs_index provides an overview, get_docs_page retrieves specific content, get_docs_full gets everything, and search_docs finds keywords. The descriptions explicitly guide usage, making misselection unlikely.
All tools follow a consistent verb_noun pattern with snake_case: list_docs, get_docs_index, get_docs_page, get_docs_full, and search_docs. The naming is predictable and readable, using clear verbs like 'get', 'list', and 'search' paired with descriptive nouns.
With 5 tools, the count is well-scoped for a documentation server, covering discovery, navigation, retrieval, and search without being overwhelming. Each tool earns its place by addressing a specific need in the documentation workflow, from initial exploration to detailed content access.
The tool set provides complete coverage for documentation access: list_docs for discovery, get_docs_index for navigation, get_docs_page for targeted retrieval, get_docs_full for comprehensive content, and search_docs for keyword-based finding. There are no obvious gaps, and the descriptions guide agents through a logical workflow.