Skip to main content
Glama

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

Base contract & token inspector

base_contract
Read-only

Inspect Base smart contract. Inspect a Base (eip155:8453) address: contract or wallet, bytecode size, proxy detection (EIP-1967 implementation/admin/beacon, EIP-1167 minimal proxy), owner(), ERC-165 interfaces (ERC-721/1155) and ERC-20 token facts (name, symbol, decimals, total supply). Public RPC data only. Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/base/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": "base_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesContract address on Base

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond that: data comes from public RPC only, cost is $0.001 USDC per call via x402 v2 on Base, and a free demo endpoint is provided — auth/payment behavior an agent must know before calling. It does not disclose behavior for non-contract addresses or what happens when a call fails or is unpaid.

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-loaded with the action and chain before the long field enumeration; every clause carries information (outputs, data source, price, demo URL). Minor redundancy in the opening two sentences ('Inspect Base smart contract. Inspect a Base ... address') and the dense parenthetical list costs some scannability.

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?

For a single-parameter read-only inspector with no output schema, the description carries the return-value burden well by listing exactly which attributes are reported, plus chain, data source, pricing, and a demo link. An agent has enough to decide whether this call answers its question.

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% and describes the address as a 'Contract address on Base', so the schema does the base work. The description adds meaning the schema lacks: the address may be a contract OR a wallet (EOA), which changes what the agent can expect back and is not conveyed by the pattern constraint.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb plus resource and pins the chain explicitly ('Inspect a Base (eip155:8453) address'), then enumerates the concrete outputs: bytecode size, EIP-1967/EIP-1167 proxy detection, owner(), ERC-165 interfaces, and ERC-20 facts. This separates it from eth_contract by chain, though it never explicitly routes the agent away from base_wallet despite accepting wallet addresses.

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 field list — an agent can infer this is the tool for on-chain contract/token metadata on Base — but there is no explicit when-to-use, when-not, or named alternative. No prerequisite or fallback guidance is given for addresses that turn out to be EOAs.

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