Skip to main content
Glama

Caelara Labs Document Utilities

universal_data_bridge

Convert data between CSV, XML and JSON with format auto-detection and type inference

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": {
      "data": "<data>",
      "to": "<to>"
    },
    "name": "universal_data_bridge"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget format: json|csv|xml
dataYesInput document (string) or JSON value
fromNoSource format: auto|csv|xml|json (default auto)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two real behavioral traits beyond the schema: automatic source-format detection and type inference during conversion. However, it says nothing about lossiness of type inference, error behavior on malformed input, or whether output is a string or structured value.

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?

A single front-loaded sentence naming the verb, the format set, and the two notable behaviors. There is no filler or redundancy.

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 three-parameter converter with no output schema, the description covers what the tool does but not what it returns (a string in the target format?) or how failures surface. Adequate as a minimum-viable definition, but it leaves the agent guessing about the response.

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 description coverage is 100%, so the parameters are already fully documented and the baseline is 3. The description adds only marginal meaning, chiefly that 'auto' for the source format implies detection rather than a fixed format.

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 uses a specific verb (Convert) plus the concrete resource set (CSV, XML, JSON), so the tool's function is unambiguous. It stops short of explicitly differentiating itself from overlapping siblings like csv_to_typed_json and xml_to_json_clean.

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?

Usage is only implied by the stated purpose as a general-purpose multi-format converter; there is no explicit when-to-use, when-not-to-use, or pointer to the specialized single-direction siblings. The phrase 'format auto-detection' hints that the source format need not be supplied, but no guidance is given on preferring this tool over the narrower converters.

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