Crypto Bot Audit + Market Data (x402 paid)

Native balance for one address

chain_balance

Read-onlyIdempotent

Native coin balance (wei plus a decimal string) at the latest block, with the chain's symbol so the number cannot be misread as USD. Costs $0.001 USDC per call. Chains: base, ethereum, arbitrum, bsc, polygon, optimism, avalanche. Byte-identical to GET /chain/balance?chain=base&address=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description
`ts`	No
`wei`	No	balance in wei
`note`	No
`chain`	No
`stale`	No
`caveat`	No
`reason`	No
`source`	No
`address`	No
`balance`	No	decimal-formatted native amount
`chainId`	No
`chainLabel`	No
`nativeSymbol`	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": {
+    "address": {
+      "type": "string"
+    },
+    "balance": {
+      "description": "decimal-formatted native amount",
+      "type": "string"
+    },
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chain": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "chainId": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "chainLabel": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "nativeSymbol": {
+      "type": "string"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "ts": {
+      "type": "string"
+    },
+    "wei": {
+      "description": "balance in wei",
+      "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?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false as safe. The description adds value beyond these by disclosing the return format (wei plus a decimal string), the inclusion of the chain symbol to prevent USD misreading, the per-call cost, and its byte-identical behavior to a REST endpoint—detail the annotations do not convey.

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?

Four sentences, each dense with information: result semantics, pricing, supported chains, and endpoint equivalence. No filler or redundancy—every sentence contributes to the agent's ability to use the tool.

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 present, return values need no elaboration. The description supplies cost, chain scope, block height semantics, and the exact REST equivalent, which is more than enough context for an agent to invoke this 2-parameter tool correctly.

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?

Input schema coverage is 100%: both chain and address are documented with their expected formats. The description repeats the chain list but adds no new meaning about parameters beyond what the schema already states, so the baseline of 3 applies.

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 opens with a specific verb and resource: 'Native coin balance' for 'one address', further specifying 'at the latest block' and that it returns the chain's symbol. This clearly distinguishes it from siblings like chain_balances (plural) and chain_token_balance, and the supported chains list removes ambiguity.

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?

The description gives useful context—pricing per call, supported chains, and the byte-identical REST endpoint—but does not explicitly say when to choose this tool over alternatives like chain_balances or chain_token_balance. Usage is implied by the 'one address' and 'native coin' phrasing, but no explicit when-to-use or when-not-to-use guidance is provided.

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?