Skip to main content
Glama
Sign In

AgentBIT

by app.agentbit
OverviewDiscussionsAdmin

JSON to CSV

agentbit.convert_json_csv
Read-onlyIdempotent

Convert a JSON array of objects into CSV text with a header row. Flatten structured data for spreadsheets and exports. Pay-per-call via x402 (USDC, Base).

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": {
      "input": "<input>"
    },
    "name": "agentbit.convert_json_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
_paymentNoOptional base64 x402 PAYMENT-SIGNATURE payload. Omit to receive payment requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds genuinely new behavioral context: the tool is pay-per-call via x402 with USDC on Base. It stops short of describing failure behavior for malformed JSON or how deeply nested objects are flattened.

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?

Three short sentences with the core purpose front-loaded and no filler. The payment sentence is a necessary addendum that could arguably be trimmed but carries real information.

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?

With no output schema present, the description correctly states the return shape (CSV text with a header row). For a two-parameter, non-destructive transform tool this is close to complete, though nesting/flattening semantics and error handling remain unstated.

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 coverage is only 50%: the _payment parameter is documented in the schema, but the required input parameter has no schema description. The description partially compensates by specifying that input is a JSON array of objects, but adds no format, size, or nesting guidance.

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 (convert), source format (JSON array of objects), and target format (CSV with header row). The directional detail cleanly separates it from the sibling agentbit.convert_csv_json without needing to open either schema.

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?

"Flatten structured data for spreadsheets and exports" implies the intended context but gives no explicit when-to-use versus convert_csv_json or convert_xml_json, and no exclusion conditions or prerequisites.

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

All AgentBIT toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources