Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

webdev_json_to_csv

Read-onlyIdempotent

Convert JSON arrays or objects into CSV text with customizable delimiter, quotes, headers, and nested object flattening.

Instructions

JSON to CSV Converter. Convert a JSON array of objects (or a single object) into CSV text, with a configurable delimiter, quote character, escape character, optional header row, null placeholder, boolean formatting, and optional flattening of nested objects into dotted-path columns. Use webdev_json_to_csv to turn structured JSON into spreadsheet-ready rows; for the reverse direction use webdev_csv_to_json, to pretty-print or validate JSON use format_json, and to fabricate demo rows use data_sample_data_generator. This tool only converts JSON to CSV (no reverse). Runs locally on the input you provide: read-only, non-destructive, contacts no external service, idempotent, and rate-limited (60 requests/minute for anonymous callers). Returns the CSV string plus validity, warnings, the discovered column headers, and row/column/size statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jsonYesJSON text to convert. Best results with an array of flat objects; a single object becomes one row, and non-object array items are wrapped as index/value pairs. Must not be blank.
delimiterNoField separator between columns (for example a comma, a tab, or a pipe).,
enclosureNoQuote character wrapped around fields that contain the delimiter, the quote character, or a newline. Empty string disables quoting."
escapeNoCharacter used to escape the enclosure inside a quoted field (defaults to doubling the quote, RFC 4180 style)."
includeHeadersNoEmit a header row of column names as the first line.
flattenObjectsNoExpand nested objects into dotted-path columns (parent.child). When false, nested objects are JSON-stringified into a single cell.
nullValueNoText substituted for JSON null, undefined, or non-finite numbers.
booleanFormatNoHow boolean values are rendered in cells.true/false

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
originalNoThe submitted JSON text, echoed back.
csvNoThe generated CSV text (empty string on failure).
isValidNoWhether the JSON parsed and converted successfully.
errorsNoFatal parse or conversion messages (empty when isValid is true).
warningsNoNon-fatal notices, such as nested objects being JSON-stringified.
statsNoSize and shape metrics for the conversion.
Behavior5/5

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

Describes behavior beyond annotations: 'Runs locally on the input you provide: read-only, non-destructive, contacts no external service, idempotent, and rate-limited (60 requests/minute for anonymous callers). Returns the CSV string plus validity, warnings, the discovered column headers, and row/column/size statistics.' Annotations already include readOnlyHint, destructiveHint, idempotentHint; description adds local execution, no external service, rate limits, and specific output. No contradiction.

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?

The description is concise and well-structured. First sentence states purpose, then detailed conversion options, followed by usage guidelines, behavioral transparency, and output summary. Every sentence adds value with no redundancy.

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?

Given the tool has 8 parameters, 100% schema coverage, an output schema (mentioned), and thorough annotations, the description covers all necessary aspects: purpose, usage, behavior, parameter hints, and output. It is complete for an AI agent to correctly select and invoke the 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?

Schema description coverage is 100%, so baseline is 3. The description does not add significant meaning beyond what the schema provides for each parameter. It lists parameters but does not elaborate on semantics or provide usage examples. Score is adequate.

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?

The description clearly states the tool converts JSON to CSV, specifying the input as 'JSON array of objects (or a single object)' and output as 'CSV text'. It distinguishes itself from siblings like webdev_csv_to_json (reverse), format_json (pretty-print/validate), and data_sample_data_generator (fabricate rows).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly states when to use: 'turn structured JSON into spreadsheet-ready rows'. Provides clear alternatives: 'for the reverse direction use webdev_csv_to_json, to pretty-print or validate JSON use format_json, and to fabricate demo rows use data_sample_data_generator'. Also mentions 'This tool only converts JSON to CSV (no reverse).'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server