Skip to main content
Glama

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

CSV to JSON: convert CSV text into a JSON array of objects

csv_to_json
Read-only

Convert CSV (comma, semicolon, tab or pipe; delimiter detected automatically; quoted fields supported) to a JSON array of objects using the first row as keys. Numbers stay as text unless numbers=true. Use to load spreadsheet exports into an agent. Example: text=name,age Ada,36. 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": "csv_to_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe CSV text, first row is the header
numbersNotrue to turn numeric cells into numbers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, non-idempotent, closed-world. The description adds genuinely new behavior: automatic delimiter detection, quoted-field handling, numbers left as text by default, and the per-call pricing/free-tier model including that failed calls are free. 'Reads or computes only and changes nothing' partially restates readOnlyHint, and 'repeats are not free' usefully reinforces non-idempotence, so nothing contradicts the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Capability is front-loaded correctly and the example is useful, but pricing, payment rails (x402 USDC / card key / credits), and free-tier terms are packed into the same paragraph as conversion semantics, creating noise an agent must sift through. The 'Example: text=name,age Ada,36.' run-on is also awkwardly formatted.

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?

For a two-parameter, no-output-schema converter with full schema coverage and complete annotations, the description covers input format, delimiter behavior, header semantics, type coercion default, and cost model. Nothing an agent needs in order to call it correctly is missing.

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%, so the baseline is 3, but the description adds real semantics beyond the schema: it states the default behavior that numeric cells stay text unless numbers=true, which the schema does not make explicit. It also documents the header-row contract for text. This is meaningful added value rather than restatement.

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 precise verb and resource pair: convert CSV text into a JSON array of objects keyed by the first row. It also names the accepted delimiters and quoted-field support, so an agent can tell it apart from json_to_csv (opposite direction) and csv_to_markdown without inspecting the schema.

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 usage context ('load spreadsheet exports into an agent') and an inline example, which is enough to know when this is the right tool. It does not name an alternative or state exclusions (e.g., when to prefer json_to_csv or a table extractor), 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.