Skip to main content
Glama

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

Proxy implementation, Arbitrum

arb_proxy
Read-only

Find the implementation behind a proxy contract on Arbitrum One: 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=0xaf88d065e77c8cC2239327C5EDb3A432268e5831. 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": "arb_proxy"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes0x contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: specific error semantics with HTTP codes (400 malformed, 422 no code), the fact that failed calls are uncharged, per-call pricing and free-tier behavior, and the note that repeats are not free – which usefully explains the idempotentHint=false annotation. It also explicitly confirms the read/compute-only nature. It stops just short of describing the shape of the return value (how 'kind' and the slots are presented).

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 purpose and method coverage, then usage, then errors, then pricing – a sensible order with no filler sentences. Minor redundancy in the pricing tail ('first 25 free; failed calls free' followed by 'each call is charged, so repeats are not free') that could be tightened.

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?

With one required string param and no output schema, the description covers purpose, standards probed, failure modes, and commercial terms well. The remaining gap is the return shape: it says it 'names the kind found' but not how the implementation address and slot findings are returned, which matters for a decoding tool.

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?

Single parameter with 100% schema description coverage, so the schema already carries the meaning. The description adds a concrete example address and the malformed-address → 400 behavior, which is a modest addition beyond the schema's '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+resource: 'Find the implementation behind a proxy contract on Arbitrum One', and enumerates exactly which standards are probed (EIP-1967 impl/beacon/admin, EIP-1822, legacy OZ layout, EIP-1167). It also names the cross-sell sibling contract_risk, so an agent can distinguish this from the per-chain *_proxy tools and from risk tooling.

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 an explicit alternative for when this tool is not sufficient ('for a fuller risk verdict use contract_risk'). The failure conditions (no code, malformed address) are also stated as usage boundaries.

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.