Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_docs_xml_to_json_clean

Convert XML text into clean JSON with @-prefixed attributes and repeated tags as arrays, simplifying parsing for document workflows.

Instructions

[Document Utilities] Convert XML to clean JSON (attributes prefixed with @, repeated tags to arrays) Measured p50 10 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://docs.caelaralabs.com.

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": "caelara_docs_xml_to_json_clean"
  }
}

Input Schema

NameRequiredDescriptionDefault
xmlYesXML text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does add real value by disclosing the output shape conventions and latency (p50 10 ms / p95 14 ms), plus the fact that a remote endpoint is called. It omits error behavior on malformed XML, input size limits, and any auth requirements for the referenced endpoint.

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?

Two tightly packed sentences with the core purpose and conventions front-loaded. The benchmark and endpoint line is slightly boilerplate but short and informative, so no serious waste.

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 single-input transformation with no output schema, the description supplies the essential output conventions and performance profile. The main residual gap is failure behavior on invalid XML, which an agent would want before calling.

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?

Only one parameter exists at 100% schema coverage, so the schema already documents 'xml'. The description's @-prefix and array-collapsing notes describe output shape rather than the input parameter, adding little beyond what the schema provides.

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 names a specific verb and resource ('Convert XML to clean JSON') and even states the mapping conventions (@-prefixed attributes, repeated tags to arrays), so the tool is distinguishable from siblings like csv_to_typed_json or html_to_clean_text. It stops short of explicitly contrasting itself with any named alternative.

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 bracket tag '[Document Utilities]' and the verb imply the conversion context, but there is no explicit statement of when to pick this over a sibling converter or any prerequisite noted beyond the endpoint URL. Usage must be inferred from the name and purpose.

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

Deploy Server

Other Tools