Skip to main content
Glama

data-api-code

xml_format_and_to_json

Pretty-print and balance-check XML documents and extract tag hierarchy counts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "xml_format_and_to_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and falls short. It does not state whether filePath reads from disk, whether text takes precedence over filePath, what happens on malformed or unbalanced XML (error vs. lenient report), or whether the operation is read-only and safe to repeat. 'Balance-check' implies a validation report but the shape of that feedback is never characterized.

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 compact sentence with no filler, and the main operation is front-loaded. It is efficient, though the terseness is partly what leaves the gaps elsewhere.

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

Completeness2/5

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

For a tool with two undocumented optional inputs, no annotations, and no output schema, the description is too thin. An agent cannot determine input selection, error behavior, or whether the JSON conversion implied by the name is part of the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain both parameters, and it explains neither. 'XML documents' loosely implies the text parameter holds XML content, but filePath is completely unaddressed and there is no indication of mutual exclusivity, precedence, or formatting of the path.

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

Purpose3/5

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

The description names specific operations (pretty-print, balance-check, extract tag hierarchy counts), which is more than a restatement of the name. However, the tool name promises XML-to-JSON conversion and the description never mentions JSON output at all, leaving the agent unsure whether conversion happens and what the result looks like. That gap between name and stated purpose keeps it at vague-but-directional rather than clearly differentiated.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among siblings (e.g. yaml_json_convert or json_schema_validate_and_mock). In particular, nothing says whether to pass raw XML via text or a path via filePath, which is the primary decision an agent must make before calling.

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