x402 agent toolkit: service finder, payment safety, Solana & web tools

by dev.workers.moneytools.x402-pay-precheck

JSON formatter, validator & path query

json_format

Read-onlyIdempotent

Validate JSON (error line + context), pretty-print/minify/sort keys, measure depth and size, and pick a value by path like a.b[0].c. Free: 10 calls/day; then $0.001/call via x402 (MCP params._meta["x402/payment"] or HTTP) or X-API-Key credits. [served by tools.moneytools.dev]

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": "<json>"
    },
    "name": "json_format"
  }
}

Input Schema

Name	Required	Description
`op`	No	pretty \| minify
`json`	Yes	JSON text
`path`	No	e.g. a.c[1]
`sortKeys`	No	true/false

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds genuinely useful non-structural context: the free quota of 10 calls/day, per-call pricing, and the two payment paths (MCP params._meta["x402/payment"] or HTTP / X-API-Key). It does not describe rate-limit failure behavior or what a validation error payload looks like, though the output schema likely covers the shape.

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 before pricing details. The pricing clause is dense but operationally necessary. The trailing server attribution is minor noise.

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 an output schema present and annotations covering the safety profile, the description only needs to convey capabilities, cost, and auth, all of which it does. The remaining gap is sibling differentiation against json_query for path extraction.

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 baseline is 3, but the description adds real meaning beyond the schema by enumerating the operation repertoire (validate, pretty, minify, sort keys, measure, path query) that the loosely-typed op parameter selects from. It also gives a concrete path syntax example (a.b[0].c) clarifying the path parameter's grammar.

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 uses concrete verbs and names the full operation set: validate with error line/context, pretty-print/minify/sort keys, measure depth and size, and extract a value by path. The resource (JSON text) is unambiguous. It stops short of distinguishing itself from the sibling json_query, which appears to cover overlapping path-query territory.

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?

Usage is implied by the enumerated operations, and the cost/auth model (free tier, x402 payment, X-API-Key) is spelled out. However, there is no explicit when-to-use vs when-not guidance or routing to siblings such as json_query, json_repair, or json_schema_validate.

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

All x402 agent toolkit: service finder, payment safety, Solana & web tools tools Inspect

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

Need Help?