Skip to main content
Glama

convert_document

Converts documents between markdown, JSON, YAML, HTML, CSV, TXT, and JSONL formats using absolute input and output paths; auto-detects formats when not specified.

Instructions

Convert documents. Input/Output: md, json, yaml, yml, html, csv, txt, jsonl, ndjson.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "inputPath": "<inputPath>",
      "outputPath": "<outputPath>"
    },
    "name": "convert_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
prettyNoPretty-print output (optional, default true)
inputPathYesAbsolute path to input document
outputPathYesAbsolute path for output document (include extension)
inputFormatNoInput format (auto-detected if not provided)
outputFormatNoOutput format (auto-detected if not provided)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and provides almost none: it does not say whether outputPath is overwritten, whether parent directories are created, whether conversion is lossy for tabular formats, or how errors on unsupported conversions surface. Only the format set is disclosed.

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?

Two short sentences, front-loaded with the action, with the format list compactly presented. It is efficient, though the second sentence is a bare list that could have carried more useful information in the same space.

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

Completeness2/5

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

For a five-parameter, no-annotation, no-output-schema mutation tool that writes files, the definition says nothing about overwrite semantics, error behavior, or destination handling. The format enumeration alone is not enough for an agent to invoke it confidently on real files.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description's format list roughly mirrors the enums but actually omits 'rst' and 'markdown' (present in the schema) and adds nothing about the meaning of pretty, inputFormat/outputFormat auto-detection, or path requirements.

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

Purpose4/5

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

The description gives a clear verb+resource ('Convert documents') and enumerates supported input/output formats. It does not, however, distinguish this tool from close siblings such as batch_convert or convert_dev_format, so an agent must infer that this handles single documents in general-purpose formats.

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

Usage Guidelines2/5

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 is given: nothing about single vs. batch conversion (batch_convert), developer-oriented formats (convert_dev_format), or discovering formats (get_supported_formats). The agent has to guess the routing from names alone.

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