Crypto Bot Audit + Market Data (x402 paid)

ERC-1155 balance of one id

chain_1155_balance

Read-onlyIdempotent

balanceOf(account, id) for a multi-token contract, formatted with whatever supply unit the contract uses — the read a Zora/Sudoswap-style position tracker needs, which an ERC-20 or ERC-721 lookup cannot answer. Costs $0.001 USDC per call. Chains: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche. Byte-identical to GET /chain/1155-balance?chain=base&token=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913&account=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913&tokenId=1.

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]
`account`	Yes	holder address [required]
`tokenId`	Yes	token id (decimal) [required]

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`note`	No
`chain`	No
`stale`	No
`token`	No
`caveat`	No
`reason`	No
`source`	No
`account`	No
`chainId`	No
`tokenId`	No
`readable`	No
`supported`	No
`balanceRaw`	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": {
+    "account": {
+      "type": "string"
+    },
+    "balanceRaw": {
+      "type": "string"
+    },
+    "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"
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "supported": {
+      "type": "boolean"
+    },
+    "token": {
+      "type": "string"
+    },
+    "tokenId": {
+      "type": "string"
+    },
+    "ts": {
+      "type": "string"
+    }
+  },
+  "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?

Adds non-obvious behavior beyond annotations: cost per call ($0.001 USDC) and formatting behavior ('formatted with whatever supply unit the contract uses'). These are not available in schema or annotations, and the description does not contradict the readOnlyHint/idempotentHint annotations.

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 longer than strictly necessary but well-structured: purpose first, then cost, then chains, then a concrete REST equivalent. Each sentence adds value and the tool is not buried in fluff. Slightly verbose, but not rambling.

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?

Covers the essential aspects for a read-only balance lookup: purpose, differentiation, cost, supported chains, and formatting behavior. The output schema handles return-value documentation, so the description need not explain that. It does not mention edge cases like invalid token or account, but that is minor for this kind of utility.

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 each parameter (chain, token, account, tokenId) is already documented with concise descriptions. The description's example URL underscores parameter usage but does not introduce new semantics beyond what the schema provides. Baseline 3 is appropriate.

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 states the exact operation (balanceOf for ERC-1155), specifies the contract type, and clearly differentiates from ERC-20/721 lookups. The mention of 'the read a Zora/Sudoswap-style position tracker needs' grounds it in a concrete use case, making the tool's purpose unambiguous.

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?

Provides clear context on when this tool is appropriate (ERC-1155 balance) and explicitly notes that ERC-20/721 lookups are insufficient. However, it does not name specific sibling tools like chain_1155_batch for multi-token queries or chain_1155_check for other checks, leaving the alternative selection partly implicit. The chain list and cost also help set expectations.

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?