Skip to main content
Glama

JSON to CSV for launch exports

toolfound_json_to_csv
Read-onlyIdempotent

Convert a small flat JSON export into a downloadable spreadsheet, with explicit limits and formula protection. Returns an evidence-bounded result and the canonical web tool URL.

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

Input Schema

NameRequiredDescriptionDefault
jsonYesA JSON array of flat objects (no nested objects or arrays), for example an analytics or launch export. Each object becomes one CSV row and the keys become the column headers.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
linksYes
errorsNo
summaryYes
sectionsYes
canonical_result_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / json / description
      Added value: +"A JSON array of flat objects (no nested objects or arrays), for example an analytics or launch export. Each object becomes one CSV row and the keys become the column headers."
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already carry readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description genuinely adds "formula protection" (CSV injection sanitization) and the return of a canonical web tool URL, but "evidence-bounded result" and "explicit limits" are opaque jargon that do not disclose what is actually bounded or what the limits are.

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 compact sentences with the core operation front-loaded and no filler. Minor deduction for compressed phrases like "evidence-bounded result" that spend words without conveying meaning.

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 simple one-parameter conversion tool with a full schema and an output schema, an agent has nearly everything needed to call it. The remaining gap is that the advertised "explicit limits" and the sanitization behavior are asserted rather than described, which matters for anyone deciding whether an input is too large or too nested.

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 at 100% schema coverage, the schema already explains that the value is a JSON array of flat objects with keys becoming headers. The description's "small flat" wording reinforces the size/nesting constraint but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

"Convert a small flat JSON export into a downloadable spreadsheet" names a specific verb (convert) and both resource forms (JSON in, CSV out), which is enough for an agent to identify the operation. It stops short of naming how it differs from plausible neighbors such as toolfound_csv_deduplicator, so it is clear but not sibling-differentiated.

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 phrase "small flat JSON export" and "explicit limits" imply the applicable input class, and the schema confirms the 12,000-character cap and flat-object restriction. But the description never states when to reach for this tool versus another, nor does it spell out the limits it advertises.

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