Skip to main content
Glama
Sign In

Csv

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Json To Csv

json_to_csv
Read-onlyIdempotent

Serialize an array of JSON objects (or arrays) to CSV (keyless, offline). Object keys become the header (union of all keys, in first-seen order). Fields are quoted when needed.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rows": [
        {
          "age": 30,
          "city": "New York",
          "name": "Alice"
        },
        {
          "age": 25,
          "city": "Los Angeles",
          "name": "Bob"
        }
      ]
    },
    "name": "json_to_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesAn array of objects (or arrays) to serialize.
delimiterNoField delimiter (default ",").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "rows": [
+      {
+        "age": 30,
+        "city": "New York",
+        "name": "Alice"
+      },
+      {
+        "age": 25,
+        "city": "Los Angeles",
+        "name": "Bob"
+      }
+    ]
+  },
+  {
+    "delimiter": "\t",
+    "rows": [
+      {
+        "price": 9.99,
+        "product": "Widget",
+        "quantity": 100
+      },
+      {
+        "price": 19.99,
+        "product": "Gadget",
+        "quantity": 50
+      }
+    ]
+  }
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations provide readOnlyHint, idempotentHint, and openWorldHint, indicating safe, deterministic behavior. The description adds details about header merging and quoting, but 'offline' is undefined and could mislead agents expecting network dependencies. No contradiction with annotations.

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 sentences, front-loaded with action, no extraneous words. Every sentence adds value: main purpose, then key behavioral details.

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?

Given rich annotations and full schema coverage, the description adequately covers input-output transformation. However, missing details about return format (CSV string vs file), 'offline' meaning, and potential size limits. Not a major gap but could be more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for both parameters. The description adds semantic context about how 'rows' keys become headers and when quoting occurs, which goes beyond bare schema definitions.

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?

Description clearly states the verb 'Serialize' and the resource 'array of JSON objects to CSV', with specific details about header formation (union of all keys in first-seen order) and quoting behavior. It differentiates from sibling 'csv_to_json' which would perform the inverse operation.

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?

No explicit guidance on when to use this tool versus alternatives like 'csv_to_json' or other serialization tools. The phrase 'keyless, offline' is ambiguous and does not clarify use cases or exclusions.

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

All Csv toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources