Crypto Bot Audit + Market Data (x402 paid)

Every receipt in one block

chain_block_receipts

Read-onlyIdempotent

eth_getBlockReceipts in a single paid call: per-transaction gas, status and log count, plus where the block's total fees went — instead of one receipt read per transaction. Costs $0.001 USDC per call. Chains: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche. Byte-identical to GET /chain/block-receipts?chain=base&block=latest.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`block`	No	block number or latest\|safe\|finalized\|earliest\|pending (default "latest")
`chain`	Yes	chain key: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche [required]

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`cap`	No
`note`	No
`rows`	No
`chain`	No
`count`	No
`stale`	No
`caveat`	No
`reason`	No
`source`	No
`chainId`	No
`truncated`	No
`chainLabel`	No
`blockNumber`	No
`failedCount`	No
`feesPaidWei`	No
`successCount`	No
`totalGasUsed`	No
`uniqueSenders`	No
`aggregatedOver`	No
`feesPaidNative`	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": {
+    "aggregatedOver": {
+      "type": "integer"
+    },
+    "blockNumber": {
+      "type": "integer"
+    },
+    "cap": {
+      "type": "integer"
+    },
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chain": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chainId": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "chainLabel": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "count": {
+      "type": "integer"
+    },
+    "failedCount": {
+      "type": "integer"
+    },
+    "feesPaidNative": {
+      "type": "string"
+    },
+    "feesPaidWei": {
+      "type": "string"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "rows": {
+      "items": {},
+      "type": "array"
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "successCount": {
+      "type": "integer"
+    },
+    "totalGasUsed": {
+      "type": "string"
+    },
+    "truncated": {
+      "type": "boolean"
+    },
+    "ts": {
+      "type": "string"
+    },
+    "uniqueSenders": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive. The description adds valuable behavioral details beyond annotations: the call costs $0.001 USDC, supported chains are enumerated, and it is byte-identical to a specific REST endpoint, giving agents information about cost, compatibility, and network coverage.

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?

The description is a single dense sentence that packs purpose, cost, supported chains, and the alternative method without redundancy. It's slightly long but every clause earns its place, and the core purpose is front-loaded before supporting details.

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?

With an output schema present, return structure is covered. The description completes the picture with cost, chain list, and equivalence to the REST call. Nothing essential for correct invocation is missing, though error handling or rate limits are not mentioned (minor gap).

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?

The input schema already provides complete descriptions for both 'block' and 'chain' (100% coverage). The description adds no extra parameter semantics—it doesn't explain parameter formats, defaults, or constraints beyond what the schema documents. Baseline 3 is appropriate when schema covers parameters fully.

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 the specific verb 'eth_getBlockReceipts' on the resource 'block receipts', lists the exact data returned (per-transaction gas, status, log count, fee distribution), and explicitly contrasts with per-transaction reads, making it unmistakable what this tool does and how it differs from siblings.

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 clearly implies when to use this tool—when you need all receipts for a block rather than one at a time—and gives the equivalent REST endpoint for reference. It doesn't name the sibling tool 'chain_receipt' explicitly, but the contrast 'instead of one receipt read per transaction' is a strong usage signal.

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?