API Acre

crypto.base-contract-read

Read-onlyIdempotent

Execute one bounded read-only eth_call against a resolved Base mainnet block, retain call and block evidence, and optionally decode caller-specified ABI output types.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`contract`	Yes	The 20-byte Base mainnet contract address to read
`block_tag`	No	Base block tag resolved once before executing the read	safe
`call_data`	Yes	ABI-encoded eth_call data, including the function selector
`gas_limit`	No	Bounded execution allowance for the read-only call
`from_address`	No	Optional msg.sender context; no private key or transaction is used
`output_types`	No	Optional primitive ABI output types used to decode a successful result; arrays and tuples are intentionally excluded

Output Schema

TableJSON Schema

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

AddedAug 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds valuable context: 'bounded' (gas limit), 'resolved Base mainnet block' (block resolution once), 'retain call and block evidence' (evidence retention), and the limitation that only primitive ABI types are decodable. This goes beyond structured data.

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?

One dense sentence that front-loads the core action ('Execute...') and packs in essential qualifiers ('bounded', 'read-only', 'resolved', 'retain evidence', 'optionally decode') without waste. Every clause earns its place.

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?

Given the rich schema (6 params, output schema) and clear annotations, the description provides enough high-level context: it explains the tool's scope (single call), block resolution, evidence retention, and optional decoding. It does not elaborate on error handling or response structure, but those are covered by the output schema and specifications.

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% and each parameter has a detailed description (e.g., block_tag 'resolved once', gas_limit 'bounded', from_address 'no private key or transaction'). The main description does not add significant per-parameter meaning beyond these schema descriptions, so baseline 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 names a specific verb ('Execute') and resource ('read-only eth_call against a resolved Base mainnet block'), and clarifies scope with 'one bounded' and 'optionally decode caller-specified ABI output types'. This clearly distinguishes it from sibling tools like base-contract-inspect or base-event-logs.

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 (e.g., when a low-level contract read is needed) but does not explicitly state when to use this tool over alternatives or when not to use it. It provides no exclusion criteria or named sibling alternatives, so guidance is limited to what can be inferred from the stated purpose.

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?