ohos-mcp-unofficial
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 |
|---|---|
| find_docsA | Search through HarmonyOS/OpenHarmony application development documentation. Use this to find UI components, APIs, or architectural guidance. |
| read_docA | Read the full content of a specific documentation file to get code examples and detailed API usage. |
| list_doc_topicsA | List all available documentation categories to understand the structure of the HarmonyOS SDK. |
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 3 tools
Each tool has a clearly distinct purpose: searching, reading, and listing documentation topics. There is no overlap or ambiguity between them.
All three tools follow the consistent verb_noun pattern with underscores: find_docs, read_doc, list_doc_topics. The naming is uniform and predictable.
Three tools is well-scoped for a documentation lookup server. Each tool addresses a necessary step in the workflow without unnecessary bloat.
The tool set covers the full documentation workflow: discover topics, search for specific docs, and read full content. No critical operations are missing for the stated purpose.