Agent Decision & Evidence Tools (MCP + x402)

28-chain read-only RPC batch

rpc_read_batch

Read-only

Run 1-20 standard read-only JSON-RPC requests as one paid call across 28 EVM mainnets. Set one default chain for the batch or override it with an optional chain field on each request. Includes public-node failover, decoded Error/Panic reverts and source evidence; signing, state-changing convenience methods and transaction broadcasting are unavailable.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	No	Default chain used when a request entry has no chain override.	base
`requests`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`tool`	No
`chain`	No
`error`	No
`chains`	No
`result`	No
`charged`	No	When present on an error, false means the failed result is uncharged.
`message`	No
`missing`	No
`receipt`	No
`settled`	No	When present on an error, false means no settlement occurred.
`took_ms`	No
`unknown`	No
`accepted`	No
`contract`	No
`node_used`	No
`read_only`	No
`retryable`	No
`error_code`	No
`extensions`	No
`chain_count`	No
`multi_chain`	No
`status_code`	No
`did_you_mean`	No
`nodes_failed`	No
`request_count`	No
`missing_checks`	No
`partial_evidence`	No
`mixed_chain_batch`	No
`transport_attempts`	No
`transport_failures`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedSep 6, 2026

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

addedInput schema / properties / chain / description

Added value: +"Default chain used when a request entry has no chain override."

removedInput schema / properties / chain / title
```
Removed value: -"Chain"
```
changedInput schema / properties / requests / items / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / properties / requests / items / properties

Added value: +{
+  "chain": {
+    "description": "Optional per-request chain override for mixed-chain batches.",
+    "type": "string"
+  },
+  "id": {
+    "description": "Caller-provided JSON-RPC correlation ID.",
+    "oneOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "integer"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "jsonrpc": {
+    "const": "2.0",
+    "default": "2.0",
+    "type": "string"
+  },
+  "method": {
+    "description": "Allowlisted read-only JSON-RPC method.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "params": {
+    "default": [],
+    "description": "JSON-RPC positional array or named-parameter object.",
+    "oneOf": [
+      {
+        "type": "array"
+      },
+      {
+        "type": "object"
+      }
+    ]
+  }
+}

addedInput schema / properties / requests / items / required
```
Added value: +[
+  "method"
+]
```
addedInput schema / properties / requests / maxItems
```
Added value: +20
```
addedInput schema / properties / requests / minItems
```
Added value: +1
```
removedInput schema / properties / requests / title
```
Removed value: -"Requests"
```

removedInput schema / title

Removed value: -"rpc_read_batch_toolArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "contract",
+        "read_only",
+        "request_count",
+        "mixed_chain_batch",
+        "took_ms",
+        "result",
+        "receipt",
+        "extensions"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "description": "Structured result contract for rpc_read_batch. A success satisfies the documented success branch. A domain or tool error includes error and is not a successful settlement; unpaid x402 requirements are carried by the transport wrapper.",
+  "properties": {
+    "accepted": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "chain": {
+      "type": "string"
+    },
+    "chain_count": {
+      "type": "integer"
+    },
+    "chains": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "charged": {
+      "description": "When present on an error, false means the failed result is uncharged.",
+      "type": "boolean"
+    },
+    "contract": {
+      "type": "string"
+    },
+    "did_you_mean": {
+      "additionalProperties": true,
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "error": {
+      "oneOf": [
+        {
+          "type": "string"
+        },
+        {
+          "additionalProperties": true,
+          "properties": {
+            "code": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "message": {
+              "type": "string"
+            },
+            "param": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "type": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "message"
+          ],
+          "type": "object"
+        }
+      ]
+    },
+    "error_code": {
+      "type": "string"
+    },
+    "extensions": {
+      "additionalProperties": true,
+      "properties": {
+        "delivery-receipt": {
+          "additionalProperties": true,
+          "properties": {
+            "how_to_verify": {
+              "type": "string"
+            },
+            "issued_at": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "issuer": {
+              "type": "string"
+            },
+            "issuer_key": {
+              "type": "string"
+            },
+            "key_id": {
+              "type": "string"
+            },
+            "result_hash": {
+              "type": "string"
+            },
+            "service": {
+              "type": "string"
+            },
+            "signature": {
+              "type": "string"
+            },
+            "signed_message": {
+              "type": "string"
+            },
+            "standard": {
+              "const": "eucompliance-receipt/2",
+              "type": "string"
+            },
+            "subject": {
+              "type": "string"
+            },
+            "valid_until": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "verify_url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "standard",
+            "service",
+            "subject",
+            "result_hash",
+            "issued_at",
+            "valid_until",
+            "issuer",
+            "issuer_key",
+            "key_id",
+            "verify_url",
+            "how_to_verify",
+            "signature",
+            "signed_message"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "delivery-receipt"
+      ],
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "missing": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "missing_checks": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "mixed_chain_batch": {
+      "type": "boolean"
+    },
+    "multi_chain": {
+      "type": "boolean"
+    },
+    "node_used": {
+      "type": "string"
+    },
+    "nodes_failed": {
+      "items": {},
+      "type": "array"
+    },
+    "partial_evidence": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "read_only": {
+      "type": "boolean"
+    },
+    "receipt": {
+      "additionalProperties": true,
+      "properties": {
+        "how_to_verify": {
+          "type": "string"
+        },
+        "issued_at": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "issuer": {
+          "type": "string"
+        },
+        "issuer_key": {
+          "type": "string"
+        },
+        "key_id": {
+          "type": "string"
+        },
+        "result_hash": {
+          "type": "string"
+        },
+        "service": {
+          "type": "string"
+        },
+        "signature": {
+          "type": "string"
+        },
+        "signed_message": {
+          "type": "string"
+        },
+        "standard": {
+          "const": "eucompliance-receipt/2",
+          "type": "string"
+        },
+        "subject": {
+          "type": "string"
+        },
+        "valid_until": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "verify_url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "standard",
+        "service",
+        "subject",
+        "result_hash",
+        "issued_at",
+        "valid_until",
+        "issuer",
+        "issuer_key",
+        "key_id",
+        "verify_url",
+        "how_to_verify",
+        "signature",
+        "signed_message"
+      ],
+      "type": "object"
+    },
+    "request_count": {
+      "type": "integer"
+    },
+    "result": {
+      "oneOf": [
+        {
+          "additionalProperties": true,
+          "type": "object"
+        },
+        {
+          "items": {},
+          "type": "array"
+        }
+      ]
+    },
+    "retryable": {
+      "type": "boolean"
+    },
+    "settled": {
+      "description": "When present on an error, false means no settlement occurred.",
+      "type": "boolean"
+    },
+    "status_code": {
+      "type": "integer"
+    },
+    "took_ms": {
+      "type": "integer"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "transport_attempts": {
+      "type": "integer"
+    },
+    "transport_failures": {
+      "items": {},
+      "type": "array"
+    },
+    "unknown": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedSep 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already set readOnlyHint=true and destructiveHint=false, but the description adds meaningful behavior beyond that: the call is paid, it supports public-node failover, it returns decoded Error/Panic reverts and source evidence, and it refuses state-changing methods. This materially changes what an agent should expect from invocation. It does not contradict the annotations. Minor gaps remain on rate limits and cost structure, keeping it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with zero filler. The core action and scope are front-loaded, the chain-configuration rule follows, and the final sentence packs features and exclusions without redundancy. Every clause earns its place and nothing repeats the schema verbatim.

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?

For a 40-sibling toolset with a complex batch input and an output schema present, the description covers the essentials: chain span, batch size limits, cost, chain override mechanics, failover behavior, revert error decoding, and unavailable operations. Gaps are the unenumerated method allowlist, the vague 'source evidence' phrase, and absent cost/rate-limit details, but the output schema carries return-value documentation.

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 roughly 50%, and the schema itself already documents chain, id, method, params, and jsonrpc with usable descriptions. The description adds genuine composite semantics — the default-chain-plus-per-request-override mental model and the allowlist framing — which helps an agent craft a correct batch. However, it doesn't elaborate individual parameter details beyond what the schema states, so a 3 (baseline-plus) is appropriate.

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 opens with a specific verb and resource: 'Run 1-20 standard read-only JSON-RPC requests as one paid call across 28 EVM mainnets.' This precisely scopes what the tool does and distinguishes it from specialized single-purpose siblings like tx_status, wallet_balance, and market_data, which are all singular reads rather than a multi-chain batch RPC facility.

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?

The description gives clear context for when the tool fits: batch read-only calls across 28 chains with per-batch or per-request chain selection. It also states explicit exclusions ('signing, state-changing convenience methods and transaction broadcasting are unavailable'), which tells an agent when not to reach for it. It stops short of naming alternatives like tx_preflight or x402_purchase_guard, so it doesn't fully fulfill the 'alternatives' criterion for a 5.

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

All Agent Decision & Evidence Tools (MCP + x402) tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.