Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

XML to JSON converter: convert an XML document into JSON

xml_to_json
Read-only

XML to JSON for any XML document: attributes become "@name" keys, text becomes "#text" (or the value itself when an element only holds text), and repeated child elements become arrays. DOCTYPEs and external entities are refused, so nothing outside the document is ever loaded. Up to 100,000 characters. Use to read XML feeds, SOAP responses and config files in an agent. Example: xml=PenInk. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "xml": "<xml>"
    },
    "name": "xml_to_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
xmlYesThe XML document

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that DOCTYPEs and external entities are refused (an XXE-related security property), imposes a 100,000 character ceiling, and states that repeated calls are billed and not free — consistent with and explanatory of idempotentHint=false. Annotations only cover safety flags, so this added operational disclosure is substantive.

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?

Front-loaded with the conversion semantics and constraints before the example, use cases, pricing and safety note. Most sentences earn their place, though "Reads or computes only and changes nothing" largely restates readOnlyHint=true/destructiveHint=false and the pricing is slightly verbose.

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

Completeness5/5

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

With no output schema, the description carries the return-shape burden and does so precisely (attributes to "@name", text to "#text" or bare value, repeated elements to arrays), plus security, size limits and cost. Nothing an agent needs to call this correctly is missing.

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 100% for the single 'xml' parameter, so baseline would be 3. The description adds a size constraint ("Up to 100,000 characters") and a concrete XML example that the schema does not contain, giving real meaning beyond the terse "The XML document" field description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource pair ("XML to JSON for any XML document") and immediately defines the conversion mapping, which distinguishes it from siblings like csv_to_json and yaml_to_json that share the same to-JSON shape but different input formats.

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

Usage Guidelines4/5

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

Gives concrete use cases ("read XML feeds, SOAP responses and config files in an agent"), which is real when-to-use guidance. It offers no when-not guidance or routing to preview/validation alternatives, but the input-format framing of the name plus the use cases leave little ambiguity.

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.