Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

JSON to CSV, array to table: convert a JSON array of objects into CSV

json_to_csv
Read-only

Convert a JSON array of objects to CSV with a header row built from all keys. Nested values are written as JSON. Use to export API results to a spreadsheet. Example: text=[{"name":"Ada","age":36},{"name":"Alan","age":41}]. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "text": "<text>"
    },
    "name": "json_to_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesA JSON array of objects

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with "Reads or computes only and changes nothing." It adds pricing and failure behavior that annotations cannot express: $0.01/call, first 25 free, failed calls free, and the explicit warning that repeats are charged because idempotentHint is false. Return format details remain thin, but that is a modest gap.

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?

Front-loads the conversion semantics, then the use case, example, and billing terms. All sentences are relevant, though the billing and read-only clauses make it slightly denser than needed for a one-parameter converter.

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, non-destructive converter with no output schema, the definition covers input shape, output behavior, and cost model. It would be stronger with a note on what happens with heterogeneous keys or non-object elements in the array.

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% for the single text parameter, so the baseline is 3. The description adds the worked example array, which clarifies that a JSON array string is expected rather than a JSON object, but adds little else about the parameter.

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?

States a specific verb and resource ("Convert a JSON array of objects to CSV") plus the exact shape of the output ("header row built from all keys", "Nested values are written as JSON"). That distinguishes it clearly from siblings like csv_to_json and json_to_yaml, which run the opposite direction.

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?

Gives a concrete use case ("Use to export API results to a spreadsheet") and an inline example input, which tells an agent the expected call shape. It does not name an exclusion or an alternative sibling, so it stops short of full routing guidance.

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.