Agent Revenue Network

Deterministic JSON Diff · Exact JSON Paths

json_diff

Read-onlyIdempotent

Discover a deterministic structural JSON diff between before and after values. Paid execution compares arrays by index and returns up to 1,000 added, removed or changed records with exact JSON paths and before/after evidence; it does not generate JSON Patch. Use json_normalize for stable serialization or json_schema_check for validity. This free MCP discovery call does not execute the advertised capability and does not charge; it returns the exact x402 endpoint, price and payment guide for execution.

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": {
      "before": "<before>",
      "after": "<after>"
    },
    "name": "json_diff"
  }
}

Input Schema

Name	Required	Description	Default
`after`	Yes	New JSON value to compare with before.
`before`	Yes	Original JSON value.

Output Schema

Name	Required	Description
`price`	Yes
`method`	Yes	HTTP method for paid execution.
`endpoint`	Yes	Canonical absolute ARN HTTP URL to POST the same tool arguments to for paid execution.
`protocol`	Yes	Payment protocol required by the HTTP execution endpoint.
`instruction`	Yes	How to execute the capability after receiving the payment requirement.
`paymentGuide`	Yes	Public setup guide with a working x402 v2 Base-mainnet client example.
`paymentRequired`	Yes	Always true for paid ARN capabilities exposed over MCP.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 20, 2026

changedOutput schema / properties / endpoint / description

Previous value: -"ARN HTTP path to POST the same tool arguments to for paid execution."New value: +"Canonical absolute ARN HTTP URL to POST the same tool arguments to for paid execution."

addedOutput schema / properties / endpoint / format
```
Added value: +"uri"
```

addedOutput schema / properties / method

Added value: +{
+  "const": "POST",
+  "description": "HTTP method for paid execution.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "paymentRequired",
-  "protocol",
-  "endpoint",
-  "price",
-  "paymentGuide",
-  "instruction"
-]New value: +[
+  "paymentRequired",
+  "protocol",
+  "method",
+  "endpoint",
+  "price",
+  "paymentGuide",
+  "instruction"
+]

Changed2 schema fields changedOct 8, 2026

addedOutput schema / properties / paymentGuide

Added value: +{
+  "description": "Public setup guide with a working x402 v2 Base-mainnet client example.",
+  "format": "uri",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "paymentRequired",
-  "protocol",
-  "endpoint",
-  "price",
-  "instruction"
-]New value: +[
+  "paymentRequired",
+  "protocol",
+  "endpoint",
+  "price",
+  "paymentGuide",
+  "instruction"
+]

Changed5 schema fields changedOct 2, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / description

Added value: +"Input for a deterministic structural comparison of two JSON values."

addedInput schema / properties / after / description

Added value: +"New JSON value to compare with before."

addedInput schema / properties / before / description
```
Added value: +"Original JSON value."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "description": "MCP payment instruction. Calling the MCP tool itself does not charge or execute the paid operation.",
+  "properties": {
+    "endpoint": {
+      "description": "ARN HTTP path to POST the same tool arguments to for paid execution.",
+      "type": "string"
+    },
+    "instruction": {
+      "description": "How to execute the capability after receiving the payment requirement.",
+      "type": "string"
+    },
+    "paymentRequired": {
+      "const": true,
+      "description": "Always true for paid ARN capabilities exposed over MCP.",
+      "type": "boolean"
+    },
+    "price": {
+      "additionalProperties": false,
+      "properties": {
+        "amount": {
+          "description": "Atomic asset amount.",
+          "type": "string"
+        },
+        "asset": {
+          "description": "Settlement asset.",
+          "type": "string"
+        },
+        "display": {
+          "description": "Human-readable current price.",
+          "type": "string"
+        },
+        "network": {
+          "description": "CAIP-2 settlement network identifier.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "amount",
+        "asset",
+        "network",
+        "display"
+      ],
+      "type": "object"
+    },
+    "protocol": {
+      "const": "x402",
+      "description": "Payment protocol required by the HTTP execution endpoint.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "paymentRequired",
+    "protocol",
+    "endpoint",
+    "price",
+    "instruction"
+  ],
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: arrays are compared by index, results cap at 1,000 added/removed/changed records with JSON paths and before/after evidence, no JSON Patch output, and the free call charges nothing but returns an x402 endpoint, price and payment guide. This is exactly the execution-model disclosure the annotations cannot carry.

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?

Front-loaded with the core capability, then output limits, then exclusions, then alternatives. Dense but every sentence carries routing or behavioral information; the x402/payment sentence is long but necessary given the discovery/execution split.

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

Completeness5/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 described, and the description still covers comparison semantics, record caps and the discovery/paid-execution model. An agent has everything needed to decide to call it and to interpret the free-call result.

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% for both required params, so baseline is 3. The description adds real comparison semantics not in the schema ('compares arrays by index'), which affects how before/after inputs are interpreted.

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 and resource ('deterministic structural JSON diff between before and after values') and explicitly scopes what it does not produce ('does not generate JSON Patch'). It also names sibling tools (json_normalize, json_schema_check) that an agent might confuse with it.

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?

Explicitly routes to alternatives with their conditions: json_normalize for stable serialization, json_schema_check for validity. It also clarifies the free-discovery vs paid-execution split. It stops short of stating when json_diff itself is the wrong choice (e.g., text/table comparison belongs to tabular_diff), so it falls just under full coverage.

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

All Agent Revenue Network 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?