API Acre

crypto.base-account-snapshot

Read-onlyIdempotent

Read point-in-time ETH, native USDC, and up to four caller-selected ERC-20 balances plus account nonce and contract-code status at one resolved Base mainnet block.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`address`	Yes	A 20-byte EVM address on Base mainnet
`block_tag`	No	Base block tag resolved once and reused for the complete snapshot	safe
`token_contracts`	No	Optional caller-selected ERC-20 contracts whose balanceOf, decimals, and symbol methods are read at the same resolved block

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Structured Base account snapshot result
`meta`	Yes
`service`	Yes
`version`	Yes
`request_id`	Yes	Unique request identifier

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedAug 17, 2026

addedOutput schema / properties / meta / properties / next_actions / items / properties / checkout_path
```
Added value: +{
+  "pattern": "^/try/",
+  "type": "string"
+}
```
addedOutput schema / properties / meta / properties / next_actions / items / properties / executes_automatically
```
Added value: +{
+  "const": false,
+  "type": "boolean"
+}
```

addedOutput schema / properties / meta / properties / next_actions / items / properties / handoff_path

Added value: +{
+  "description": "Free full contract and spend-capped command handoff; reading it does not execute or purchase the follow-up.",
+  "pattern": "^/catalog/",
+  "type": "string"
+}

addedOutput schema / properties / meta / properties / next_actions / items / properties / handoff_payment_required
```
Added value: +{
+  "const": false,
+  "type": "boolean"
+}
```
addedOutput schema / properties / meta / properties / next_actions / items / properties / maximum_atomic_usdc
```
Added value: +{
+  "pattern": "^[1-9][0-9]*$",
+  "type": "string"
+}
```
addedOutput schema / properties / meta / properties / next_actions / items / properties / sample_path
```
Added value: +{
+  "pattern": "^/samples/",
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

changedOutput schema / properties / meta / properties / next_actions / items / required

Previous value: -[
-  "service",
-  "title",
-  "reason",
-  "method",
-  "path",
-  "price",
-  "input_template",
-  "use_output",
-  "authorization_required"
-]New value: +[
+  "service",
+  "title",
+  "reason",
+  "method",
+  "path",
+  "price",
+  "input_template",
+  "use_output",
+  "handoff_path",
+  "checkout_path",
+  "sample_path",
+  "maximum_atomic_usdc",
+  "handoff_payment_required",
+  "executes_automatically",
+  "authorization_required"
+]

Changed4 schema fields changedAug 11, 2026

addedInput schema / properties / token_contracts

Added value: +{
+  "description": "Optional caller-selected ERC-20 contracts whose balanceOf, decimals, and symbol methods are read at the same resolved block",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 4,
+  "title": "Token Contracts",
+  "type": "array"
+}

addedOutput schema / properties / data / properties / requestedTokenCount
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / data / properties / tokenSource
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / data / properties / tokens

Added value: +{
+  "description": "Balances for only the caller-selected token contracts; this is not a discovered or complete portfolio.",
+  "items": {
+    "properties": {
+      "balanceAtomic": {
+        "pattern": "^[0-9]+$",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "balanceFormatted": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "contract": {
+        "pattern": "^0x[0-9a-fA-F]{40}$",
+        "type": "string"
+      },
+      "decimals": {
+        "maximum": 255,
+        "minimum": 0,
+        "type": [
+          "integer",
+          "null"
+        ]
+      },
+      "standard": {
+        "const": "ERC-20",
+        "type": "string"
+      },
+      "status": {
+        "enum": [
+          "ok",
+          "unavailable"
+        ],
+        "type": "string"
+      },
+      "symbol": {
+        "maxLength": 64,
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "warnings": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "contract",
+      "standard",
+      "status",
+      "symbol",
+      "decimals",
+      "balanceAtomic",
+      "balanceFormatted",
+      "warnings"
+    ],
+    "type": "object"
+  },
+  "maxItems": 4,
+  "type": "array"
+}

Changed2 schema fields changedAug 11, 2026

addedOutput schema / properties / meta / properties / next_actions

Added value: +{
+  "description": "Optional separately priced follow-up calls. Each action requires a new payment challenge and explicit buyer authorization.",
+  "items": {
+    "properties": {
+      "authorization_required": {
+        "const": true,
+        "type": "boolean"
+      },
+      "input_template": {
+        "description": "Client-side template only: $request refers to the original input, $result to this response, and $json(...) serializes its argument. The server does not execute the follow-up.",
+        "type": "object"
+      },
+      "method": {
+        "const": "POST",
+        "type": "string"
+      },
+      "path": {
+        "pattern": "^/v1/",
+        "type": "string"
+      },
+      "price": {
+        "pattern": "^\\$[0-9]+",
+        "type": "string"
+      },
+      "reason": {
+        "type": "string"
+      },
+      "service": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "use_output": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "service",
+      "title",
+      "reason",
+      "method",
+      "path",
+      "price",
+      "input_template",
+      "use_output",
+      "authorization_required"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / meta / required

Previous value: -[
-  "duration_ms",
-  "cached",
-  "sources",
-  "warnings"
-]New value: +[
+  "duration_ms",
+  "cached",
+  "sources",
+  "warnings",
+  "next_actions"
+]

AddedAug 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish read-only, non-destructive, idempotent behavior. The description adds valuable behavioral context by emphasizing 'point-in-time' and 'one resolved Base mainnet block,' indicating all reads are consistent at the same block. It also clarifies that native USDC and ETH are always included while other tokens are optional, which 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?

A single, concise sentence that front-loads the action ('Read') and packs in all essential details without redundancy. No filler words, and the structure is easy to parse.

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?

The tool has a rich output schema, so return values need no explanation. The description covers the key behavioral aspects: what data is read (ETH, USDC, ERC-20s, nonce, code status), the block resolution semantics, and the optional token selection. It is complete for an agent to understand when and how to invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds meaning by clarifying that ETH and native USDC are always included in the snapshot, while token_contracts is optional and limited to four ERC-20s. It also explains the significance of the block_tag as the resolved point-of-consistency, going beyond the schema field descriptions.

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 uses a specific verb 'Read' and identifies the exact resource: point-in-time ETH, native USDC, up to four caller-selected ERC-20 balances, account nonce, and contract-code status at one resolved Base mainnet block. This clearly distinguishes it from sibling tools like crypto.base-account-status, which likely provides a simpler current-state view.

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 conveys clear context: it is for reading a consistent snapshot at a chosen block, including token balances beyond the native asset. However, it does not explicitly name alternative tools or state when not to use it, so it stops short of full explicit exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All API Acre 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?