mcp-taro-docs
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| taro-official-query-assetsA | Query Taro official online docs (docs.taro.zone) via sitemap URL matching. Returns asset_ids for taro-official-get-assets. |
| taro-official-get-assetsA | Fetch online official docs page content by asset_ids returned from taro-official-query-assets. |
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 2 tools
The two tools have clearly distinct purposes: one finds asset IDs via sitemap matching, the other fetches content using those IDs. No overlap or confusion between them.
Both tool names follow the same verb-noun pattern with a consistent 'taro-official-' prefix, making the interface predictable and uniform.
With only two tools, the server feels minimal but is arguably sufficient for its narrow scope of querying and fetching docs. It borders on being too thin for a full-featured docs server.
The query-then-get workflow is logically complete for retrieving specific doc pages. Minor gaps exist, such as no direct URL fetch or list-all capability, but the core task is well covered.