Skip to main content
Glama

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

Proxy implementation, Optimism

op_proxy
Read-only

Find the implementation behind a proxy contract on Optimism: 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=0x0b2C639c533813f4Aa9D7837CAf62653d097Ff85. 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": "op_proxy"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes0x contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint/destructiveHint, the description discloses the detection surface, the error contract (400 for malformed address, 422 for address without code, both uncharged), and the billing model ($0.01/call, first 25 free, failed calls free). The line "each call is charged, so repeats are not free" directly explains the non-obvious idempotentHint=false annotation instead of contradicting it.

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?

Content is front-loaded: detection scope first, then usage routing, then errors, example, and pricing. It is dense but nearly every clause carries information an agent needs; the pricing/credits sentence is longer than strictly necessary but is material for a metered endpoint.

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 one-parameter tool with no output schema, the description covers what is read, what is returned, failure modes, cost, and the alternative tool. Nothing an agent needs to decide or invoke correctly is missing.

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% for the single address parameter, so baseline is 3. The description adds practical meaning by supplying a concrete example address and the validation consequences of a malformed or codeless address, which the schema's "0x contract address" does not convey.

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?

"Find the implementation behind a proxy contract on Optimism" gives a specific verb, resource, and chain. The description then enumerates exactly what is inspected (EIP-1967 implementation/beacon/admin slots, EIP-1822 UUPS, legacy OpenZeppelin layout, EIP-1167 minimal-proxy bytecode) and states the return ('names the kind found'), so it is distinguishable from sibling chain variants and from op_is_contract.

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?

"Use before trusting or decoding a contract whose code can be swapped by its admin" gives a clear triggering condition, and "for a fuller risk verdict use contract_risk" names an explicit alternative. There is no explicit when-not guidance (e.g. for non-proxy contracts), but the context is unambiguous for a single-purpose lookup tool.

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.