Crypto Bot Audit + Market Data (x402 paid)

Did one storage slot change?

chain_storage_diff

Read-onlyIdempotent

The same slot read at two blocks: previous, current, and whether they differ — the primitive behind 'what did this contract's state actually move between those two dates'. Costs $0.001 USDC per call. Chains: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche. Byte-identical to GET /chain/storage-diff?chain=base&address=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913&slot=0x0&blockA=latest&blockB=latest.

Input Schema

TableJSON Schema

Name	Required	Description
`slot`	Yes	storage slot (hex, up to 32 bytes) [required]
`chain`	Yes	chain key: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche [required]
`blockA`	No	older block (number or latest\|safe\|finalized\|earliest) (default "safe")
`blockB`	No	newer block (number or tag) (default "latest")
`address`	Yes	target address, 0x + 40 hex [required]

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`note`	No
`slot`	No
`chain`	No
`stale`	No
`blocks`	No
`caveat`	No
`reason`	No
`source`	No
`valueA`	No
`valueB`	No
`address`	No
`asUintA`	No
`asUintB`	No
`chainId`	No
`changed`	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": {
+    "address": {
+      "type": "string"
+    },
+    "asUintA": {
+      "type": "string"
+    },
+    "asUintB": {
+      "type": "string"
+    },
+    "blocks": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chain": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chainId": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "chainLabel": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "changed": {
+      "type": "boolean"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "slot": {
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "ts": {
+      "type": "string"
+    },
+    "valueA": {
+      "type": "string"
+    },
+    "valueB": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond that: a $0.001 USDC per-call cost, supported chains, and a byte-identical REST endpoint. Nothing here contradicts the annotations.

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?

Four concise sentences front-load the core purpose, then add cost, chain support, and endpoint equivalence. No filler or redundant restatement of the schema.

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?

With an output schema present, return values are covered. The remaining operational context—purpose, pricing, chain list, and exact endpoint—is fully provided, and annotations cover the safety profile. An agent can select and invoke this tool correctly.

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 100%, so the baseline is 3. The description adds the previous/current labels and an example URL showing blockA and blockB, but it does not materially extend the parameter meaning already present in the schema.

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 states a precise operation: reading the same storage slot at two blocks and reporting previous, current, and whether they differ. This clearly distinguishes it from single-slot readers like chain_storage and range readers like chain_storage_range, and the phrase primitive behind the state-move question reinforces the intent.

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?

It provides clear usage context: this is the tool to answer whether a specific contract storage slot moved between two blocks or points in time. It does not explicitly name alternatives or when-not-to-use scenarios, but the two-block slot-diff framing makes the intended use unambiguous.

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?