Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_docs_universal_data_bridge

Convert data between CSV, XML and JSON with automatic format detection and type inference, so you can bridge documents across formats without manual parsing or schema setup.

Instructions

[Document Utilities] Convert data between CSV, XML and JSON with format auto-detection and type inference 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": {
      "data": "<data>",
      "to": "<to>"
    },
    "name": "caelara_docs_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 observedv1.0.1

TDQS

B3.2/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 useful operational traits – auto-detection, type inference, and measured latency (p50 10 ms, p95 14 ms with a dated source) – which is more than most definitions offer. However, it says nothing about input size limits, malformed-input behavior, error modes, or whether type inference can be disabled.

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 and dense: purpose first, then performance evidence, then docs URL. Three short clauses with no padding. The trailing 'Calls https://docs.caelaralabs.com' is low value but minor.

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?

With no output schema and no annotations, the description should still state what a caller gets back from a conversion – a serialized string? a JSON value? how type inference surfaces in the output. That is missing. Performance and detection details are covered, so it is adequate but leaves a real gap.

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 all three parameters are already documented, making 3 the baseline. The description reinforces the semantics of `from` (auto-detection) and adds that type inference applies to converted values, but it adds no syntax, size, or precedence detail beyond the schema.

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?

Clear verb+resource: 'Convert data between CSV, XML and JSON', plus two named capabilities (format auto-detection, type inference). An agent knows exactly what it does. It does not, however, distinguish itself from narrower siblings like caelara_docs_csv_to_typed_json or caelara_docs_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 Guidelines2/5

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

No when-to-use or when-not-to-use guidance, and no mention of the more specific sibling converters that overlap with this one. The only implicit guidance is 'format auto-detection', which suggests `from` can be left as auto, but nothing is stated about choosing this tool over the single-format converters.

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