Skip to main content
Glama
s3eidat

S3eidat Tools MCP

by s3eidat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

JSON to CSV

json_to_csv
Read-onlyIdempotent

Convert JSON to CSV with one row per object, flatten nested fields to dotted columns, and guard against spreadsheet formulas.

Instructions

Convert JSON to CSV. An array of objects becomes one row per object with nested objects/arrays flattened to dotted columns (address.city, tags.0); an array of arrays is written as-is. Fields are quoted only when needed (delimiter, quotes, line breaks, leading/trailing spaces); CRLF line ends. A formula guard (on by default) prefixes cells starting with = + - @ so spreadsheets don't run them. Give "text" or a file "path". Web version: https://s3eidat.github.io/csv-json/

Input Schema

NameRequiredDescriptionDefault
bomNoStart with a UTF-8 BOM so Excel reads non-English text correctly.
pathNoOr: a path to a JSON file (UTF-8; use this for big inputs).
safeNoFormula guard: prefix cells like =SUM(A1) with ' (default true).
textNoThe JSON (array or object) as inline text.
headerNoInclude a header row (default true).
outputNoOptional: also write the result to this file path (or folder ending in "/"). The result text is then left out of the reply. Results over 1,000,000 characters are always written to a file.
delimiterNoDelimiter: "auto" (comma), ",", ";", "tab" or "|".auto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses important behavior: nested objects/arrays are flattened to dotted columns, arrays of arrays are written as-is, quoting is minimal, line endings are CRLF, and the formula guard is on by default. That is strong behavioral context for an agent.

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?

The description is front-loaded and dense with useful conversion details, with no redundant restatement of the name. The trailing web-version URL is not necessary for tool selection or invocation, so it is slightly less than maximally concise.

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 seven-parameter converter with no output schema, the description covers input interpretation, nesting behavior, quoting, line endings, and safety behavior well. It does not explicitly describe the return value shape, but the schema and the conversion statement make the output context sufficiently clear.

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 the schema already documents every parameter thoroughly. The description adds some contextual meaning around 'text' versus 'path' and the formula guard, but most parameter-level detail remains in the schema, matching the baseline for high coverage.

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 states a specific verb and resource -- converting JSON to CSV -- and immediately explains concrete conversion semantics for arrays of objects, nested flattening, arrays of arrays, quoting, line endings, and formula guarding. It is clearly distinguishable from the reverse sibling csv_to_json.

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

Usage Guidelines4/5

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

It gives clear input-mode guidance -- 'Give "text" or a file "path"' -- and describes output formatting behavior. It does not explicitly compare against alternatives such as csv_to_json or json_format, so it stops short of full when/when-not routing.

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

Deploy Server

Other Tools