Skip to main content
Glama

apex-dev

Json toolbox

json_toolbox
Read-onlyIdempotent

Deterministic JSON Schema validator, structural JSON diff, dot-path query, flatten/unflatten, and JSON<->CSV converter. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

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": {
      "op": "<op>"
    },
    "name": "json_toolbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
bNoSecond JSON value when op=diff.
opYesOperation: validate, diff, flatten, unflatten, to_csv, from_csv, or query.
csvNoCSV text when op=from_csv.
dataNoPrimary JSON value or JSON string.
pathNoDot/bracket path when op=query.
schemaNoJSON Schema object when op=validate.
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered externally. The description adds real context beyond that: it is deterministic, it costs $0.001 per call, and it is billed via x402 in specific currencies (USDC on Arc/Base/Solana, XNT on X1). It does not disclose failure modes, e.g. what happens if `payment` is invalid or if the wrong `op`-specific field is supplied.

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, front-loaded with the capability list followed by the commercial/payment mechanics; nothing is padding. The currency enumeration is slightly verbose, but it is concrete and load-bearing for making the paid call correctly.

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?

For a seven-operation multiplexer with no output schema, the description says nothing about what each operation returns, e.g. a validation verdict vs. a diff patch vs. CSV text. The payment handshake and capability list are well covered, and annotations carry the safety profile, but the divergent return shapes are a meaningful remaining gap for a tool this broad.

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 100%, so every parameter, including the `op` enum values and the conditional fields (`b`, `csv`, `path`, `schema`), is already documented in structured form. The description adds no argument-level detail beyond restating the operation set and the presence/absence of `payment`. Baseline 3 is appropriate when the schema carries the semantic load.

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?

The description names a specific resource (JSON) and enumerates the exact operations it performs: schema validation, structural diff, dot-path query, flatten/unflatten, and JSON<->CSV conversion. These map one-to-one onto the `op` values in the schema, so an agent can tell immediately which capability it is invoking, and none of the listed siblings (web fetch, DNS, PDF conversion) overlap with this scope.

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?

It gives an explicit, actionable call protocol: call once without `payment` to receive terms, then call again with `payment`. That is a genuine when/how-to-use instruction that an agent would otherwise have to guess. What it lacks is any statement of when *not* to use the tool or which of the seven operations to prefer in an ambiguous case.

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.

Resources