Crypto Bot Audit + Market Data (x402 paid)

Up to 10 contract reads, one payment

chain_multicall

Read-onlyIdempotent

Batched eth_call: ten (target, calldata) pairs settled once, each answered independently so one reverting view cannot fail the rest. A tenth of the per-call cost of doing them one at a time. Costs $0.001 USDC per call. Chains: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche. Byte-identical to GET /chain/multicall?chain=base&calls=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913:0x95d89b41,0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913:0x18160ddd&blockTag=latest.

Input Schema

TableJSON Schema

Name	Required	Description
`calls`	Yes	up to 10 pairs, formatted 0xTo:0xCalldata,comma separated [required]
`chain`	Yes	chain key: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche [required]
`blockTag`	No	block number or latest\|safe\|finalized\|earliest\|pending (default "latest")

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`note`	No
`rows`	No
`chain`	No
`stale`	No
`caveat`	No
`reason`	No
`source`	No
`chainId`	No
`answered`	No
`blockTag`	No
`requested`	No
`chainLabel`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "answered": {
+      "type": "integer"
+    },
+    "blockTag": {
+      "type": "string"
+    },
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chain": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chainId": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "chainLabel": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "requested": {
+      "type": "integer"
+    },
+    "rows": {
+      "items": {},
+      "type": "array"
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "ts": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses partial-failure semantics ('one reverting view cannot fail the rest'), per-call pricing, supported chains, and byte-identical REST equivalence. This is exactly the behavioral context an agent needs.

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?

Dense but efficient: core operation first, then failure semantics, cost, supported chains, and a concrete example. No filler.

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?

For a read-only batch tool with full schema coverage, rich annotations, and an output schema, the description covers selection, invocation format, cost, and edge-case behavior. Nothing essential is missing.

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 the baseline is 3. The description adds a concrete URL example showing exact call formatting (0xTo:0xCalldata, comma-separated) and blockTag usage, which reinforces the schema's parameter descriptions.

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: batched eth_call over up to ten (target, calldata) pairs. The phrase 'each answered independently' and the title's 'contract reads' distinguish it from single-call siblings like chain_call.

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 to use it: multiple contract reads, with a cost advantage ('A tenth of the per-call cost of doing them one at a time'). It does not explicitly name chain_call or state when not to use it, but the batching and pricing make the intended use obvious.

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

All Crypto Bot Audit + Market Data (x402 paid) 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?