Skip to main content
Glama

CSV to JSON

bursia_csv_to_json
Read-onlyIdempotent

Convert CSV (first row = headers) into JSON rows. Max 5,000 rows. 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": {
      "csv": "<csv>"
    },
    "name": "bursia_csv_to_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvYesCSV text; the first row holds the column names.
separatorNoOne-character column separator. Default ",". Use ";" for spreadsheets in Spanish locales.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / csv / description
      Added value: +"CSV text; the first row holds the column names."
    • addedInput schema / properties / separator / description
      Added value: +"One-character column separator. Default \",\". Use \";\" for spreadsheets in Spanish locales."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description adds real value on top: a hard 5,000-row limit and 'pure computation, free' (no side effects, no quota cost). It stops short of saying what happens on oversized input or malformed rows.

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?

Two short sentences, front-loaded with the operation and the header assumption, followed by the two constraints that matter. No filler.

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?

With no output schema, the description should say the result is an array of row objects keyed by header names; 'into JSON rows' implies but doesn't confirm that shape. Everything else an agent needs (input format, limits, cost, safety) is present.

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 both parameters are already documented, and the description's 'first row = headers' merely restates the schema. The separator parameter, including the Spanish-locale hint, is only covered by the schema, not the description.

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?

States a specific verb and resource ('Convert CSV ... into JSON rows') plus the key input assumption ('first row = headers'), so the agent knows exactly what transformation happens. It does not name the reverse sibling bursia_json_to_csv, but the direction is unambiguous from the name and description.

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?

'Max 5,000 rows. Pure computation, free.' gives constraints and cost context but no explicit when-to-use/when-not-to-use or pointer to alternatives such as bursia_json_to_csv or bursia_json_format. Usage is only implied by the tool's obvious purpose.

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