Skip to main content
Glama

zato: Ethereum & Base Data API (pay-per-call x402)

Ethereum contract inspector (proxy, owner, token standard)

eth_contract
Read-only

Inspect Ethereum smart contract. Ethereum smart contract introspection: contract or wallet, bytecode size, proxy detection (EIP-1967 implementation/admin/beacon, EIP-1167 minimal proxy, legacy OpenZeppelin proxy), owner(), ERC-165 interfaces (ERC-721/1155) and ERC-20 token facts. Ethereum mainnet, public RPC data. Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/eth/contract

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "eth_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesContract address on Ethereum mainnet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only give readOnlyHint and openWorldHint; the description adds real context beyond them: public RPC data source, per-call cost of $0.001 USDC via x402 on Base, a free demo URL, and the fact that the target may be a wallet rather than a contract. It stops short of stating behavior for invalid or non-contract addresses and gives no latency or failure-mode info.

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?

Front-loads the purpose in the first clause, then packs the capability list efficiently. The pricing/demo sentence is useful but reads promotional and could be shortened; overall no wasted sentences, just dense phrasing.

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?

No output schema exists, so the description carries return-value burden, and it does enumerate the returned facts (bytecode size, proxy type, owner, interfaces, token facts) plus chain scope and cost. It leaves the response shape and EOA/error handling unspecified, which is a modest gap for a read-only inspector.

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?

Single required parameter with 100% schema description coverage, so the schema already carries the regex and meaning. The description only adds that the address is mainnet-scoped, which is marginal value over the structured field — the 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?

States a specific verb and resource ('Inspect Ethereum smart contract') and enumerates the exact facts produced: bytecode size, EIP-1967/EIP-1167/legacy proxy detection, owner(), ERC-165 interfaces, ERC-20 token facts. The 'Ethereum mainnet' scope cleanly separates it from the Base-oriented siblings (base_contract, base_wallet).

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?

Usage is implied by the enumeration of checks and the 'contract or wallet' framing, which signals it works on EOAs as well as contracts. However, it never states when to prefer eth_wallet or base_contract, nor any prerequisite (e.g., address must be mainnet). No explicit when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources