Crypto Bot Audit + Market Data (x402 paid)

Receipt, gas used and confirmations

chain_receipt

Read-onlyIdempotent

Status, gasUsed, effective gas price, contract created, log count and live confirmations for one hash — whether a transaction actually landed and what it cost. Costs $0.001 USDC per call. Chains: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche. Byte-identical to GET /chain/receipt?chain=base&hash=0x55bd09129b86846556030b6036d48c75865b1f8e73ee6f7df60a22a56f3cd0d4.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`hash`	Yes	transaction hash, 0x + 64 hex [required]
`chain`	Yes	chain key: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche [required]

Output Schema

TableJSON Schema

Name	Required	Description
`to`	No
`ts`	No
`from`	No
`note`	No
`chain`	No
`found`	No
`stale`	No
`caveat`	No
`reason`	No
`source`	No
`status`	No	1 = success
`chainId`	No
`costWei`	No
`gasUsed`	No
`logCount`	No
`chainLabel`	No
`blockNumber`	No
`confirmations`	No
`contractAddress`	No
`transactionHash`	No
`logsBloomPresent`	No
`cumulativeGasUsed`	No
`effectiveGasPriceGwei`	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": {
+    "blockNumber": {
+      "type": "integer"
+    },
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chain": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chainId": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "chainLabel": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "confirmations": {
+      "type": "integer"
+    },
+    "contractAddress": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "costWei": {
+      "type": "string"
+    },
+    "cumulativeGasUsed": {
+      "type": "string"
+    },
+    "effectiveGasPriceGwei": {
+      "type": "integer"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "from": {
+      "type": "string"
+    },
+    "gasUsed": {
+      "type": "string"
+    },
+    "logCount": {
+      "type": "integer"
+    },
+    "logsBloomPresent": {
+      "type": "boolean"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "1 = success",
+      "type": "integer"
+    },
+    "to": {
+      "type": "string"
+    },
+    "transactionHash": {
+      "type": "string"
+    },
+    "ts": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations cover read-only/idempotent/non-destructive behavior, and the description adds cost ($0.001 USDC per call), live confirmations, and exact returned fields such as contract-created and log count. It also gives a byte-identical endpoint reference, making the behavior transparent.

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 compact and front-loads the core result fields and purpose in the first sentence. The cost and chain enumeration are useful, though the chain list duplicates the schema and the byte-identical example is extra detail.

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 two-parameter lookup with an output schema, the description covers purpose, cost, supported chains, and required input format. Nothing essential appears missing for correct invocation.

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% and both required params are described in the schema (chain key list, 0x+64-hex format), so the description adds little beyond the schema. The expanded example URL is a useful illustration but not new semantic content.

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 deliverable — status, gasUsed, effective gas price, contract created, log count, and live confirmations — for a single hash, and explicitly frames it as answering whether a transaction landed and what it cost. This is easily distinguished from generic chain_tx or chain_tx_status siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the tool is for one hash and for confirming landing/cost, so an agent can infer when to use it. It does not name alternatives or exclusion conditions (e.g., when to prefer chain_tx_status or chain_block_receipts), so guidance is implied rather than 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?