Skip to main content
Glama

Convert CSV to JSON objects

bpj_csv_to_json
Read-onlyIdempotent

Use the first row as keys and preserve quoted commas and line breaks. Cells remain strings.

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": "bpj_csv_to_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, closed-world, non-destructive), and the description adds genuinely useful behavior beyond them: header row becomes keys, quoted commas and line breaks are preserved, and all cell values stay strings rather than being type-coerced. It stops short of stating the return shape or how malformed/ragged rows are handled.

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?

Two tight sentences with zero filler, and the key parsing rule is front-loaded. It could have opened with a single clause naming the conversion itself, which would have cost nothing and clarified the purpose.

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 one-input, no-output-schema tool, the description covers parsing rules and value typing but omits the input size cap and any statement about what is returned (array of objects) or failure behavior on malformed CSV. Adequate, but an agent could still call it incorrectly by exceeding the length limit.

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?

With a single parameter and 0% schema description coverage, the description must carry the parameter burden. It does clarify the expected input shape (first row is a header row) and output typing, but never mentions the 12,000-character maxLength limit, which is a hard constraint an agent could easily violate.

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 describes parsing semantics ('use the first row as keys') rather than stating plainly that it converts a CSV string into a JSON array of objects; that verb+resource only appears in the title. An agent can infer the transformation, but nothing distinguishes it explicitly from siblings like bpj_csv_to_markdown_table or the inverse bpj_json_to_csv beyond guesswork from names.

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 such as the markdown-table or filtered-CSV siblings. Usage is only implied by the header/quoting behavior described.

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.