Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Ethereum is-contract check

eth_is_contract
Read-only

Check whether a 0x address on Ethereum is a smart contract or a plain wallet: bytecode size, whether it is an EIP-1167 minimal proxy and which implementation it points to, and whether it is a wallet that delegates to contract code (EIP-7702; delegatedTo names the code, isContract stays false). Use before sending funds or approving a spender; for a fuller risk verdict use check_counterparty. A malformed address is rejected with 400, uncharged. Example: address=0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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_is_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes0x address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive/non-idempotent, and the description reinforces this with "reads or computes only and changes nothing" plus the non-idempotency rationale ("each call is charged, so repeats are not free"). It also discloses error behavior (malformed address rejected with 400, uncharged), pricing, and free-call allowances — genuinely useful context beyond annotations, though the pricing detail is somewhat promotional.

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?

Purpose is front-loaded and the EIP-1167/EIP-7702 details are packed efficiently. The final pricing/free-call clauses are dense and slightly commercial, but they do carry behavioral meaning about repeat-call cost.

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?

No output schema exists, yet the description effectively documents the return shape (bytecode size, proxy indicator, implementation pointer, delegatedTo vs isContract) and the error path. For a one-parameter read tool, an agent has everything needed to call and interpret it.

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?

Only one parameter and schema coverage is 100%, so the schema already documents the "0x address" input. The description adds a concrete example address, which helps format confirmation but is not deep semantic enrichment. Baseline 3 for high-coverage single-parameter schemas.

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 ("Check whether a 0x address on Ethereum is a smart contract or a plain wallet") and enumerates the exact outputs: bytecode size, EIP-1167 minimal proxy status plus implementation, and EIP-7702 delegation. The chain qualifier ("on Ethereum") also separates it from the many chain-specific *_is_contract siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use guidance ("before sending funds or approving a spender") and names an alternative with the condition that selects it ("for a fuller risk verdict use check_counterparty"). Nothing about tool selection is left to inference.

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.