Crypto Bot Audit + Market Data (x402 paid)

Many ERC-1155 positions, one payment

chain_1155_batch

Read-onlyIdempotent

balanceOfBatch over up to 10 (account, id) pairs in a single settled call — the position snapshot of a portfolio, which is otherwise one paid read per line. Costs $0.001 USDC per call. Chains: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche. Byte-identical to GET /chain/1155-batch?chain=base&token=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913&accounts=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913&tokenIds=1,2.

Input Schema

TableJSON Schema

Name	Required	Description
`chain`	Yes	chain key: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche [required]
`token`	Yes	token / NFT contract address [required]
`accounts`	Yes	up to 10 holder addresses, positionally matched to tokenIds [required]
`tokenIds`	Yes	up to 10 ids (decimal), same order as accounts [required]

Output Schema

TableJSON Schema

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

Even though readOnlyHint, idempotentHint, and destructiveHint=false already cover safety, the description adds material behavior: $0.001 USDC cost per call, a 10-pair cap, supported chains, and byte-identical REST equivalence. 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?

The main function is front-loaded and every segment—function, cost, chains, REST equivalence—carries distinct information. The long example URL is dense rather than padded.

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, full parameter descriptions, and strong annotations, the description covers purpose, cost, supported chains, batch limits, and exact endpoint equivalence. An agent has what it needs to select and invoke this tool.

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 applies and the description mostly restates positional matching and caps already in the schema. The byte-identical GET example demonstrates encoding (e.g., tokenIds=1,2) but leaves the accounts list delimiter implicit, so it adds only marginal value.

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?

Description names the exact operation (balanceOfBatch) and resource (up to 10 ERC-1155 account/id pairs) in a single settled call, and positions it as a portfolio snapshot. This is distinct from the single-position 1155 siblings and from other chain balance 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?

It clearly indicates when to use the tool: when you need a multi-position snapshot and want to avoid one paid read per line. It does not explicitly name the single-balance sibling or state when not to use it, so it falls just short of full routing guidance.

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?