Crypto Bot Audit + Market Data (x402 paid)

A short run of block headers

chain_block_series

Read-onlyIdempotent

Height, timestamp, transaction count, gas used and base fee for up to 25 consecutive blocks — the series itself, so a caller can plot throughput or fee pressure instead of taking our word for the average. Costs $0.001 USDC per call. Chains: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche. Byte-identical to GET /chain/block-series?chain=base&blocks=20.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	Yes	chain key: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche [required]
`blocks`	No	how many blocks, newest first (max 25) (default 10)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`note`	No
`rows`	No
`chain`	No
`count`	No
`stale`	No
`caveat`	No
`reason`	No
`source`	No
`window`	No
`chainId`	No
`chainLabel`	No
`secondsPerBlock`	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": {
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chain": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chainId": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "chainLabel": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "count": {
+      "type": "integer"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "rows": {
+      "items": {},
+      "type": "array"
+    },
+    "secondsPerBlock": {
+      "type": "integer"
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "ts": {
+      "type": "string"
+    },
+    "window": {
+      "additionalProperties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds useful context beyond those: the $0.001 cost, the supported chain list, the block cap, and byte-identical equivalence to the REST endpoint. No contradiction with 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?

Each sentence earns its place: fields and purpose, cost, supported chains, and REST equivalence. It is compact, front-loaded with the most decision-relevant information, and contains no filler.

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 simple read-only tool with a full output schema and clear annotations, the description is nearly complete. The only minor gap is that it does not explicitly contrast itself with single-block or stats tools, but an agent can infer this from the raw-series framing.

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 description coverage is 100%, so the baseline is 3. The description reinforces the chain list and the 'up to 25' cap, but it does not add new semantic details beyond the schema, such as how to format the blocks value as a string.

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 exactly what is returned — height, timestamp, transaction count, gas used, and base fee for up to 25 consecutive blocks — and frames it as 'the series itself.' It also ties the tool to a concrete GET endpoint, making it easy to distinguish from single-block or aggregate-stat 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?

It gives a clear use case: callers who want to plot throughput or fee pressure from raw series data rather than rely on an average. Supported chains and cost are stated, but it does not explicitly name alternatives like chain_block or chain_block_stats, so the guidance is strong but not fully explicit.

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?