MoneyTools x402 agent toolkit

JSON diff + patch

json_diff

Read-onlyIdempotent

Structural diff of two JSON values: added/removed/changed paths (JSON Pointer) and an RFC 6902-style patch. 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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "json_diff"
  }
}

Input Schema

Name	Required	Description	Default
`a`	Yes	old JSON
`b`	Yes	new JSON

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds genuinely non-inferable context: a free tier of 10 calls/day, $0.001/call thereafter, and the two payment paths (x402 via params._meta or HTTP, or X-API-Key credits) — material operational behavior an agent must know before calling.

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: purpose front-loaded, then billing constraints. Every clause carries information, though the domain tag '[served by tools.moneytools.dev]' is low-value for tool selection.

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?

An output schema exists, so return values need not be explained, yet the description still previews the output shape (paths + RFC 6902 patch). Combined with disclosed pricing and payment mechanics, an agent has enough to invoke it correctly; only sibling routing guidance is absent.

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% and both parameters (a, b) carry descriptions and examples, so the schema does the heavy lifting. The description only restates 'two JSON values' and adds no format or edge-case detail beyond what the schema already supplies — the baseline 3 for full coverage.

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?

States a specific verb and resource ('Structural diff of two JSON values') and names the output artifacts: added/removed/changed paths as JSON Pointer plus an RFC 6902-style patch. It does not explicitly contrast with siblings like text_diff or csv_diff, though the 'JSON' qualifier makes the domain implicit.

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?

No explicit when-to-use or when-not-to-use guidance, and no alternative named (e.g., text_diff for strings, json_query for extraction). Usage is implied by the purpose statement alone, which is the minimum viable level.

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

All MoneyTools x402 agent toolkit 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?