Skip to main content
Glama

Convert JSON objects to CSV

bpj_json_to_csv
Read-onlyIdempotent

Export scalar fields from an array of objects. Formula-like string cells receive an apostrophe prefix.

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

Input Schema

NameRequiredDescriptionDefault
jsonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the read-only, idempotent, non-destructive annotations, it discloses the non-obvious behavior of prefixing formula-like string cells with an apostrophe. This is valuable CSV-injection context, though column ordering, header generation, and other conversion behavior remain unstated.

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-load the operation and then state an important output-safety behavior. Both sentences add distinct information, with no filler or repetition of annotation data.

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?

For a one-parameter converter, the description, schema constraints, and annotations provide enough information for basic selection and invocation. With no output schema, the lack of detail about non-scalar field handling and basic CSV conventions prevents full completeness, but these are secondary gaps for a simple tool.

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 0% schema description coverage, the description partly compensates by specifying that the JSON content should be an array of objects. It does not explicitly connect that requirement to the string-valued `json` argument or provide a small input example, so the compensation is incomplete.

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 identifies a specific operation and scope: exporting scalar fields from an array of objects, with the title establishing CSV as the destination format. It goes beyond restating the name, although it does not explicitly differentiate itself from sibling conversion or CSV tools.

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 array-of-objects and scalar-field wording implies that the tool is intended for flat, tabular JSON data. However, there is no explicit when-to-use or when-not-to-use guidance, and it does not say whether nested objects or arrays should be preprocessed, omitted, or handled by another tool.

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.