Skip to main content
Glama
Sign In
document-mcp

document-mcp

by ExaDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List document conversions

list_document_conversions

List all supported source and target format pairs for document conversion, verifying which combinations convert_document accepts.

Instructions

Lists every (source, target) format pair convert_document actually supports, straight from documents.js's own DocumentConverter port -- the definitive source of truth for what convert_document will and will not accept as a (source, targetFormat) combination.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_document_conversions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
conversionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.8
    • changedOutput schema / properties / conversions / items / properties / source / enum
      Previous value: -[
-  "docx",
-  "pptx",
-  "xlsx",
-  "odt",
-  "odp",
-  "ods",
-  "odg",
-  "odf",
-  "markdown",
-  "pdf"
-]New value: +[
+  "docx",
+  "pptx",
+  "xlsx",
+  "odt",
+  "odp",
+  "ods",
+  "odg",
+  "svg",
+  "odf",
+  "csv",
+  "markdown",
+  "pdf"
+]
    • changedOutput schema / properties / conversions / items / properties / target / enum
      Previous value: -[
-  "docx",
-  "pptx",
-  "xlsx",
-  "odt",
-  "odp",
-  "ods",
-  "odg",
-  "odf",
-  "markdown",
-  "pdf"
-]New value: +[
+  "docx",
+  "pptx",
+  "xlsx",
+  "odt",
+  "odp",
+  "ods",
+  "odg",
+  "svg",
+  "odf",
+  "csv",
+  "markdown",
+  "pdf"
+]
  2. Addedv1.1.6

TDQS

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the burden. It explains the tool reads from documents.js's port, indicating it's a read-only operation, but doesn't detail output structure or performance. It adds value by establishing authority, but leaves some behavioral details (e.g., output format, potential errors) undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, but it is packed with purpose and context. It is efficient and front-loaded with the core function, though it could be slightly more concise by trimming the 'definitive source of truth' phrase, which is somewhat redundant with the rest.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters and an output schema exists, the description covers the key aspect: what the tool lists and its authoritative source. It doesn't detail the output format, but that's covered by the output schema. The description is adequate for a simple listing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the description doesn't need to explain parameters. The base for 0 parameters is 4, and the description appropriately focuses on what the tool returns (the format pairs), which is the needed semantic context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists every (source, target) format pair that convert_document supports, directly tying it to the definitive source of truth. It distinguishes itself from siblings by explicitly naming convert_document and framing this tool as the reference for convert_document's capabilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it: to know what convert_document will or will not accept. It doesn't explicitly say when NOT to use it, but the context of the sibling tools and the focus on format pairs make the intended use clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools