Reads XMind mind map files and converts them to Markdown, preserving hierarchical structure, notes, and labels for easy document sharing.
读取 XMind 文件并转换为 Markdown 格式。支持解析思维导图的层级结构、备注、标签等信息。
| Name | Required | Description | Default |
|---|---|---|---|
| xmind_path | Yes | XMind 文件的路径（支持相对路径或绝对路径） | |
| output_path | No | 输出 Markdown 文件的路径（可选）。如果不提供，将自动保存到 output/ 目录下，文件名与原 XMind 文件同名。 | |
| include_metadata | No | 是否在 Markdown 中包含文件元信息（默认为 true） |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It mentions supported data (hierarchy, notes, tags) but omits key behavioral traits such as file overwrite behavior, authentication needs, error handling, or output format details. Significant gaps remain.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is very short (one sentence) and front-loads the main action. It is concise, though additional details could be included without significant bloat.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no annotations, the description lacks sufficient context for correct tool usage. Missing details on output format, default behavior of output_path, error scenarios, and file system interaction.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers all 3 parameters with descriptions (100% coverage). The description adds no extra semantic value beyond schema, so baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool converts XMind files to Markdown and lists supported features (hierarchy, notes, tags). It is specific about the verb and resource, but does not explicitly differentiate from sibling tool 'read_xmind_structure', though the difference is implied.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives, no prerequisites, no when-not scenarios. The description merely states what the tool does without contextual usage advice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jiandong0718/mcp-xmind-to-markdown'
If you have feedback or need assistance with the MCP directory API, please join our Discord server