Skip to main content
Glama

JSON to CSV

bursia_json_to_csv
Read-onlyIdempotent

Convert a JSON array of objects into CSV with a header row. Returns the CSV text and the column list. Pure computation, free.

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": {
      "json": "<json>"
    },
    "name": "bursia_json_to_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
jsonYesA JSON array of objects, e.g. [{"a":1,"b":2}].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / json / description
      Added value: +"A JSON array of objects, e.g. [{\"a\":1,\"b\":2}]."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the safety profile is settled. The description adds value beyond them by disclosing the return shape ('the CSV text and the column list') when no output schema exists, plus that the operation is pure computation with no cost or external calls.

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?

Three short sentences, each carrying distinct information: the transformation, the return values, and the cost/compute profile. Front-loaded with the purpose and free of filler.

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

Completeness5/5

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

For a single-parameter, deterministic conversion utility, the description covers what the tool does, what it returns (compensating for the absent output schema), and that it is side-effect-free. Nothing an agent needs in order to invoke it correctly is missing.

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 a single required parameter with 100% schema description coverage, including an inline example, so the schema does the explanatory work. The description's phrase 'a JSON array of objects' merely restates the schema constraint and adds no new format or edge-case guidance (e.g. nested values, heterogeneous keys).

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

Purpose5/5

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

States a specific verb and resource with the exact transformation direction: convert a JSON array of objects to CSV with a header row. Because the direction (JSON→CSV) is explicit, it is inherently distinguishable from the inverse sibling bursia_csv_to_json without opening either schema.

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 description implies usage (you have a JSON array of objects and want tabular text) and adds the operational note 'Pure computation, free,' but never states when to prefer this over alternatives such as bursia_csv_to_json or bursia_json_format, nor any preconditions or exclusions.

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