Skip to main content
Glama

job_doc_to_markdown

Convert a document to Markdown (MarkItDown)

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": {
      "file_b64": "<file_b64>",
      "filename": "<filename>"
    },
    "name": "job_doc_to_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_b64Yesthe document, base64
filenameYesits file name; the extension picks the converter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing. It doesn't say whether conversion is lossy, whether tables/images are preserved, whether large base64 payloads are capped, or what the response contains. The parenthetical library reference hints at behavior but does not describe it.

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?

One short, front-loaded sentence with no filler, and the core action appears first. It is efficient, though the terse form leaves no room for the context that other dimensions need, so it is lean rather than exemplary.

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 tool is simple — two required string parameters, no nested objects — so a short description is defensible. However, with no annotations and no output schema, the description should have said what comes back (a Markdown string? a file reference?) and roughly what formats are supported. Those are real gaps for a conversion tool.

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 both parameters are already documented, and the schema itself explains that the filename extension selects the converter. The description adds no parameter-level detail beyond naming the converter. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb+resource: convert a document to Markdown, and names the underlying converter (MarkItDown). That is enough for an agent to distinguish it from the surrounding YouTube/OCR/TTS jobs. It stops short of a 5 because it doesn't contrast with any near-neighbour like the OCR job, so an agent must infer that this tool is not for scanned images.

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?

There is no explicit guidance on when to use this tool or when not to. Nothing says whether it handles scanned PDFs, images, or only text-extractable formats, which is precisely the ambiguity an agent faces against job_ocr_tesseract. Usage is only implied by the tool name and the conversion verb.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources