Skip to main content
Glama
Sign In
Delx MCP Server

Delx MCP Server

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Json To Csv

util_json_to_csv
Read-onlyIdempotent

Converts structured JSON rows into CSV format for exports, spreadsheets, and data handoff.

Instructions

Convert structured JSON rows into CSV for exports, spreadsheets, and handoff. Delx Agent Utilities are separate from the free witness protocol and may expose x402 utility pricing.

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_text": "<json_text>"
    },
    "name": "util_json_to_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
delimiterNoOptional one-character delimiter,
json_textYesJSON array or object

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds no additional behavioral context beyond the basic conversion operation, missing details like input format requirements or output structure.

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 sentences are concise, but the second sentence about pricing is not strictly necessary for describing tool function. The main purpose is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but the return type (CSV) is implied. Missing details on expected JSON structure (array of objects) and error handling. Adequate for a simple conversion but could be more complete.

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 both parameters. The description adds no extra meaning beyond what is already in the schema.

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?

The description states 'Convert structured JSON rows into CSV for exports, spreadsheets, and handoff', which clearly indicates the verb and resource. However, it does not explicitly differentiate from sibling tools like util_csv_to_json, though the reverse operation is implied.

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. The note about Delx Agent Utilities and pricing is tangential and not about usage context.

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

Deploy Server

Other Tools