Skip to main content
Glama

Caelara Labs Document Utilities

xml_to_json_clean

Convert XML to clean JSON (attributes prefixed with @, repeated tags to arrays)

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_clean"
  }
}

Input Schema

NameRequiredDescriptionDefault
xmlYesXML text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose two meaningful output conventions — attributes prefixed with @ and repeated tags collapsed into arrays — which is real behavioral value, but it says nothing about failure modes, malformed XML, whitespace/text-node handling, or return shape beyond those two rules.

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 front-loaded sentence with zero filler; the parenthetical cleanly carries the non-obvious output rules. Nothing is wasted.

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 simple single-parameter transform this covers the essentials of the output mapping, but with no output schema and no annotations, an agent still lacks any statement of error behavior or the exact JSON shape produced (e.g., root element handling).

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?

There is one parameter, fully documented in the schema as 'XML text', and the description adds no syntax, encoding, or size-format detail beyond that. With 100% schema coverage the baseline of 3 is appropriate.

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?

Specific verb and resource: 'Convert XML to clean JSON', which names both the input format and the output format unambiguously. It is easy to distinguish from siblings like csv_to_typed_json or markdown_to_sanitized_html, though the description does not explicitly do the distinguishing itself.

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?

Provides no when-to-use guidance, no prerequisites, and no mention of when an alternative (e.g., a generic bridge tool) would be preferable. The intended use is only implied by the verb 'Convert'.

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