Document Convert MCP
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 |
|---|---|
| convert_documentC | 转换文档格式，支持Word、Markdown、PDF、HTML等格式互转 |
| batch_convert_documentsB | 批量转换多个文档 |
| get_supported_formatsA | 获取支持的文档格式列表 |
| validate_documentB | 验证文档是否可以转换 |
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 4 tools
Each tool has a clearly distinct purpose: single conversion, batch conversion, format discovery, and validation. No overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern in snake_case: convert_document, batch_convert_documents, get_supported_formats, validate_document. The 'batch_' prefix clearly indicates a variant, and the naming is predictable.
Four tools is a well-scoped size for a document conversion server. Each tool covers a necessary aspect without bloat or redundancy.
The tool surface covers the full lifecycle of document conversion: discovering supported formats, validating inputs, converting a single document, and batch converting multiple documents. No obvious dead ends or missing operations.