Crypto Bot Audit + Market Data (x402 paid)

Token supply at a past block

chain_supply_at

Read-onlyIdempotent

totalSupply read at any block and diffed against now, formatted with the token's own decimals — how much of a supply was minted since a date, without an indexer. Costs $0.001 USDC per call. Chains: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche. Byte-identical to GET /chain/supply-at?chain=base&token=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913&block=latest.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`note`	No
`block`	No
`chain`	No
`stale`	No
`token`	No
`caveat`	No
`reason`	No
`source`	No
`symbol`	No
`chainId`	No
`decimals`	No
`deltaRaw`	No
`changePct`	No
`direction`	No
`latestRaw`	No
`atBlockRaw`	No
`chainLabel`	No
`blockNumber`	No
`deltaFormatted`	No
`decimalsAssumed`	No
`latestFormatted`	No
`atBlockFormatted`	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": {
+    "atBlockFormatted": {
+      "type": "string"
+    },
+    "atBlockRaw": {
+      "type": "string"
+    },
+    "block": {
+      "type": "string"
+    },
+    "blockNumber": {
+      "type": "integer"
+    },
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chain": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chainId": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "chainLabel": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "changePct": {
+      "type": "number"
+    },
+    "decimals": {
+      "type": "integer"
+    },
+    "decimalsAssumed": {
+      "type": "boolean"
+    },
+    "deltaFormatted": {
+      "type": "string"
+    },
+    "deltaRaw": {
+      "type": "string"
+    },
+    "direction": {
+      "type": "string"
+    },
+    "latestFormatted": {
+      "type": "string"
+    },
+    "latestRaw": {
+      "type": "string"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "symbol": {
+      "type": "string"
+    },
+    "token": {
+      "type": "string"
+    },
+    "ts": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the per-call cost ($0.001 USDC), supported chains, decimal formatting behavior, the diff-against-current-supply semantics, and the no-indexer implementation trait. This is substantial behavioral context that annotations alone do not provide.

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?

The description is dense but every sentence earns its place: the first sentence explains behavior, the second covers cost/chains, and the third gives a byte-identical API reference. It is 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.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich annotations, complete schema coverage, and existing output schema, the description covers everything an agent needs: operation, cost, chains, block handling, formatting, and API equivalence. No critical information for invoking it correctly is missing.

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 schema already documents chain, token, and block semantics including defaults. The description adds color about decimals and shows an exact endpoint example, but provides no parameter-level meaning beyond what the schema already carries.

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 names a specific verb and resource: totalSupply read at a block and diffed against current supply, formatted with the token's decimals. It also explains the practical outcome — how much supply was minted since a date — and clearly distinguishes this from balance/meta/transfer sibling tools.

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 frames the intended use case ('minted since a date') and adds a useful positioning cue ('without an indexer'). It does not explicitly name alternatives or exclusion conditions, but the context is specific enough for an agent to select it appropriately.

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?