Skip to main content
Glama

docs_tools_to_markdown

[$x402 pago por llamada] Convierte un documento (PDF, DOCX, etc. — el formato se detecta por contenido, no por extensión) a Markdown, vía anydoc.

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_base64": "<file_base64>"
    },
    "name": "docs_tools_to_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.
file_base64YesContenido del archivo codificado en base64 (o data URL). Se convierte a multipart/form-data internamente.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It discloses the paid-call model (x402) and that format is detected by content, which is valuable. But it omits output form (Markdown text vs. file), size/time limits, and failure modes beyond the 402 payment path—leaving moderate gaps for a compute-heavy paid tool.

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?

A single tightly written sentence, front-loaded with the payment tag then the action and resource. The parenthetical about content-based detection earns its place. Slightly dense with a tag that could be split, but no wasted text.

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?

For a paid, no-annotation, no-output-schema tool, the description should clarify what comes back (Markdown string, file, metadata) and any limits. It says 'converts to Markdown' but not the response shape or constraints, leaving an agent to infer too much.

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 (file_base64 and x_payment) are fully documented in the schema. The description adds only the payment-model tag, not parameter semantics. 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?

States a specific verb and resource: converts a document (PDF, DOCX, etc.) to Markdown via `anydoc`. The format-detection detail (by content, not extension) adds useful precision. It doesn't explicitly distinguish itself from siblings like docs_tools_ocr or web_tools_extract_article, so it stops short of a 5.

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 purpose implies when to use it (any doc→Markdown conversion), and the content-based format detection tells the agent it needn't pre-check extensions. However, there is no explicit statement of when to prefer this over docs_tools_ocr or pdf_metadata, and no prerequisites or exclusions are given.

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