Skip to main content
Glama

convert_email

Convert EML or MBOX email files to JSON, HTML, TXT, or Markdown while extracting headers, subject, and body for processing or archiving.

Instructions

Convert email files. Input: eml, mbox. Output: json, html, txt, md. Extracts headers, subject, body.

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_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyOnlyNoOnly include subject, from, to, date, body (optional)
inputPathYesAbsolute path to input email file (.eml or .mbox)
outputPathYesAbsolute path for output file (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

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden; its statement that conversion extracts headers, subject, and body adds useful context. It does not disclose whether the source remains unchanged, whether an existing output is overwritten, or how multi-message mbox input is represented.

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

Conciseness5/5

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

The description is compact and front-loaded, moving efficiently from the action to supported formats and extracted content. Every fragment contributes useful selection information without filler.

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

Completeness3/5

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

The fully described schema covers the five parameters well enough for basic invocation, including required paths and optional format detection. Nevertheless, the absence of an output schema leaves output structure unexplained, and important conversion cases such as mbox multiplicity and overwrite behavior remain unspecified.

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 of 3 applies. The description largely repeats the input and output enums and adds no further meaning for absolute paths, format auto-detection, output extensions, or bodyOnly beyond what the schema already supplies.

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 specific verb and resource—converting email files—and narrows the operation to eml/mbox inputs and json/html/txt/md outputs. The extraction of headers, subject, and body further clarifies the result, although there is no explicit differentiation from sibling converters.

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

Usage Guidelines3/5

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

The supported formats make the intended email-conversion context easy to infer. However, the description provides no explicit when-to-use or when-not-to-use guidance and does not direct the agent to an alternative for other conversion scenarios.

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