Skip to main content
Glama

Evm code

evm_code
Read-onlyIdempotent

Is this address a contract, across 8 EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Arc and Robinhood): code size, the implementation behind an EIP-1967 or ZeppelinOS proxy, and an EIP-7702 delegation. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": "evm_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoethereum (default), base, arbitrum, optimism, polygon, bnb, arc or robinhood
addressYesaddress (0x...)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chain / description
      Previous value: -"ethereum (default), base, arc or bnb"New value: +"ethereum (default), base, arbitrum, optimism, polygon, bnb, arc or robinhood"
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered; the description adds material context they cannot: cost ($0.001 per call), accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the two-step x402 handshake that changes how the call must be made. It does not state failure modes (non-contract address, unpaid second call) or the response shape in any detail.

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?

The core question is front-loaded in the first clause, followed by returned fields, scope, and then payment mechanics. It is a dense single paragraph with no filler, though the parenthetical chain enumeration and payment-rail detail make it heavier than strictly necessary.

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?

For a 3-parameter, no-output-schema tool, the description covers what is answered, which chains, what is returned, and the full payment flow. The remaining gap is edge-case behavior (non-contract addresses, expired or rejected payments), which an agent would otherwise have to discover at call time.

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%, so the chain list and address format are already documented. The description still adds meaning to the `payment` parameter by explaining that the first call returns terms to sign and the second call with a signed payload completes the purchase inside the tool call, which the schema field alone only hints at.

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?

The description opens with a precise question the tool answers ("Is this address a contract") and enumerates exactly what it returns: code size, EIP-1967/ZeppelinOS proxy implementation, and EIP-7702 delegation, scoped to 8 named chains. It never names an overlapping sibling such as address_identify or evm_call, so the boundary is inferred rather than stated.

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

Usage Guidelines4/5

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

The payment protocol is spelled out as an explicit sequence: call without `payment` to get terms, sign with your own wallet, call again with `payment`. That is concrete and actionable. What is missing is any when-to-use/when-not guidance relative to the many sibling lookup tools, or what to do when the address is an EOA.

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