API Acre

crypto.base-account-status

Read-onlyIdempotent

Check one Base mainnet wallet or contract for ETH and official USDC balances, transaction nonce, and contract-bytecode evidence at a single resolved 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 every account read	safe

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Structured Base account status 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"
+]

Changed2 schema fields changedAug 13, 2026

addedOutput schema / properties / data / properties / usdcBalance

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "atomic": {
+      "pattern": "^[0-9]+$",
+      "type": "string"
+    },
+    "contract": {
+      "const": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
+      "type": "string"
+    },
+    "decimals": {
+      "const": 6,
+      "type": "integer"
+    },
+    "formatted": {
+      "pattern": "^[0-9]+(?:\\.[0-9]+)?$",
+      "type": "string"
+    }
+  },
+  "required": [
+    "atomic",
+    "formatted",
+    "decimals",
+    "contract"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / data / properties / usdcSource
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```

AddedAug 11, 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=true and idempotentHint=true, covering the safety profile. The description adds useful behavioral context: reads are performed at a single resolved block, and only 'official USDC' is considered, which goes beyond the 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 description is a single, well-structured sentence with no superfluous words. It front-loads the main purpose and lists specific outputs efficiently.

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?

Given the tool's simplicity, the presence of a rich output schema, and strong annotations, this description covers all essential aspects. It explains what the tool does, what data it returns, and the consistency guarantee of a single resolved block.

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%, with both parameters clearly documented in the schema. The description's phrase 'single resolved block' echoes the schema's block_tag description but does not add new parameter-level information.

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 clearly states the tool checks a specific Base mainnet wallet or contract and lists the exact data returned: ETH and official USDC balances, transaction nonce, and contract-bytecode evidence. This specificity distinguishes it from generic siblings like crypto.base-account-snapshot.

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 implies usage when these specific account attributes (balances, nonce, bytecode) are needed, but it does not explicitly mention alternatives or provide when-not-to-use guidance. The sibling list includes similar tools, so more explicit differentiation would improve this dimension.

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?