Skip to main content
Glama

convert_file

Download a public PDF, CSV/TSV, XLSX/XLS, or HTML file (up to 10 MB) and convert it into structured JSON or plain text for downstream processing.

Instructions

Download a public PDF, CSV/TSV, XLSX/XLS or HTML file (max 10 MB) and convert it to structured JSON (rows, sheets, pages) or plain text. Price about $0.05. Paid per call with x402 from your XRPL_SEED wallet (XRP or RLUSD, capped by MAX_*PER_CALL and SESSION_BUDGET*). Without a wallet it returns the price quote and charges nothing. Failed calls are not charged.

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": {
      "url": "<url>"
    },
    "name": "convert_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
urlYesPublic file URL
assetNoAsset to pay with on the XRP Ledger: XRP (default) or RLUSD
formatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior5/5

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

With no annotations at all, the description carries the full burden and does so well: it discloses the cost (~$0.05), the payment rail (x402 from XRPL_SEED, XRP or RLUSD), the spending caps (MAX_*_PER_CALL, SESSION_BUDGET_*), the no-wallet fallback (price quote returned, nothing charged), and that failed calls are free. That is exactly the auth/cost/failure context an agent needs before invoking a 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?

Four tight sentences, front-loaded with what it does, then output shape, then pricing and payment, then failure behavior. No filler. The MAX_*_PER_CALL and SESSION_BUDGET_* tokens are dense but they are real configuration the caller must know about.

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?

There is no output schema, but the description still explains the return shape (rows, sheets, pages, or plain text), and it fully covers the payment/error semantics that make this tool risky to call blindly. Gaps are minor: it does not say what happens for a non-public URL, an unsupported/oversized file, or how the no-wallet quote response is structured.

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?

Schema coverage is only 50% (url and asset are described; to and format are not), but the description compensates: 'to structured JSON ... or plain text' explains the to enum, and the format list mirrors the format enum, implying the input type is detected or specified. The asset parameter is also given meaning via the XRP/RLUSD payment sentence. Some residual ambiguity remains about whether format is required or auto-detected.

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 ('Download ... and convert') plus the exact resource types (PDF, CSV/TSV, XLSX/XLS, HTML) and the two output shapes (structured JSON or plain text), with a size bound. That is far more precise than a generic 'convert file'. It stops short of naming a sibling such as web_to_markdown to draw the boundary, so it lands at 4 rather than 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?

Usage is only implied: you supply a public file URL when you want rows/sheets/pages extracted. The preconditions 'public' and 'max 10 MB' are stated, which is useful, but there is no explicit when-to-use-this-vs-alternative guidance (e.g. how it differs from web_to_markdown or call_paid_service).

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