Skip to main content
Glama

XML to Excel API - flatten any XML into a table

xml_to_excel
Read-onlyIdempotent

Turn XML (feeds, exports, orders) into an Excel or CSV table: finds the repeating row element, flattens attributes and nested tags. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.005 per call via x402 at https://radarbg.com/x402/xml-to-excel.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fileName": "orders.xml",
      "fileContent": "PG9yZGVycz48b3JkZXIgaWQ9JzEnPjxpdGVtPlBlbjwvaXRlbT48cXR5PjM8L3F0eT48L29yZGVyPjxvcmRlciBpZD0nMic+PGl0ZW0+Qm9vazwvaXRlbT48cXR5PjE8L3F0eT48L29yZGVyPjwvb3JkZXJzPg=="
    },
    "name": "xml_to_excel"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNoOr several files: [{fileName, fileContent (base64)}]
formatNoxlsx or csvxlsx
rowTagNoRow element name (optional, auto-detected)
fileNameNoFile name with extension, e.g. report.pdf
fileContentNoThe file as base64 (a data: URI is fine)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld/idempotent annotations: remote server execution, immediate file deletion and no storage, a 25 calls/day free tier, and paid pricing at $0.005 per call via x402 with the endpoint URL. That is exactly the operational context an agent needs before uploading user data.

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?

Two tight sentences: capability and flattening behavior first, then trust/privacy, then cost and endpoint. No filler, and the most decision-relevant facts are front-loaded.

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?

For a file-transformation tool with full schema coverage and no output schema, it covers inputs, privacy, and cost thoroughly. The one gap is how the result is delivered (download URL, inline base64, or binary), which an agent must discover at call time.

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 coverage is 100%, so fileName, fileContent, files, format, and rowTag are already documented in the schema. The description adds only that row detection is automatic, which lightly reinforces rowTag being optional, but supplies no base64 sizing limits or multi-file behavior detail.

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 transformation: XML in, Excel/CSV table out, and adds mechanism detail ('finds the repeating row element, flattens attributes and nested tags') that an agent can use to predict output shape. Slightly short of a 5 because it never names a sibling or says how it differs from the generic 'data_convert' conversion tool.

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?

Input examples (feeds, exports, orders) imply when the tool fits, and the output format choice is stated, but there is no explicit when-to-use/when-not guidance and no pointer to an alternative for non-XML sources. Usage must be inferred.

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