Skip to main content
Glama

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

Proxy implementation, Ethereum

eth_proxy
Read-only

Find the implementation behind a proxy contract on Ethereum: reads the EIP-1967 implementation, beacon and admin slots, EIP-1822 (UUPS), the older OpenZeppelin layout and EIP-1167 minimal-proxy bytecode, and names the kind found. Use before trusting or decoding a contract whose code can be swapped by its admin; for a fuller risk verdict use contract_risk. A malformed address is 400; an address without code is 422, both 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_proxy"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes0x contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, non-idempotent behavior, and the description reinforces that with cost semantics that explain the non-idempotent flag: failed calls are free but successful repeats are charged. It also discloses error behavior (400 malformed address, 422 address without code, both uncharged), which the annotations do not cover. The remaining gap is that it never says what is returned when the target is not a proxy at all — a key outcome for a detector.

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 core purpose and detection methods, then usage guidance, then error and cost facts — each block earns its place and there is no repetition. It is a single dense paragraph, so the pricing/billing clause runs long relative to the rest and could be tighter.

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 one-parameter read tool with full schema coverage and annotations, the definition supplies purpose, detection standards, usage trigger, an alternative, error codes, and billing behavior. The one substantive omission is the non-proxy case and the shape of the answer beyond "the kind found" (no output schema exists to cover it).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is simple, so baseline is 3; the description adds real meaning by implying the address must actually hold code (422 otherwise), giving a concrete example address, and constraining it to Ethereum. That goes beyond the schema's bare "0x contract address".

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 ("Find the implementation behind a proxy contract on Ethereum") and then enumerates exactly which detection mechanisms are read: EIP-1967 implementation/beacon/admin slots, EIP-1822 UUPS, older OpenZeppelin layout, and EIP-1167 minimal-proxy bytecode. It also states the output in essence ("names the kind found"), and the chain qualifier distinguishes it from the per-chain proxy 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 an explicit when-to-use condition — before trusting or decoding a contract whose code can be swapped by its admin — and routes the agent to a named alternative (contract_risk) for a full risk verdict. Both the trigger and the boundary against another tool are stated rather than implied.

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.