Crypto, web, finance and app data tools

Proxy Detector

proxy_check

Detect upgradeable proxies: EIP-1967 transparent/UUPS, beacon, EIP-1822, ZeppelinOS, EIP-1167 clones and Safe-style proxies, returning implementation, admin and beacon addresses. Use for audits and to fetch the real ABI.

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

Input Schema

Name	Required	Description	Default
`chain`	No		ethereum
`address`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; 'Detect ... returning implementation, admin and beacon addresses' adequately signals a read-only inspection operation. However, it does not say what happens for non-proxy addresses, whether it verifies bytecode, or anything about chain coverage, leaving meaningful behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, zero filler, and the exhaustive standard list is front-loaded before the usage note. Nothing could be cut without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the partial return-value mention is a bonus rather than a requirement. But the description omits the chain parameter's role and negative-case behavior, which matter for a detection tool that will often be called on non-proxy addresses.

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

Parameters2/5

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

Schema description coverage is 0% and the description mentions neither parameter. The `address` input is implied by 'detect' but the `chain` parameter (default 'ethereum') and the fact that non-Ethereum chains are supported are completely undocumented in both schema and description.

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 ('Detect') and resource ('upgradeable proxies') and enumerates the exact standards covered (EIP-1967, UUPS, beacon, EIP-1822, ZeppelinOS, EIP-1167, Safe-style), which distinguishes it cleanly from siblings like contract_info or storage_slot.

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

Usage Guidelines3/5

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

'Use for audits and to fetch the real ABI' gives a use-context cue, but there are no explicit exclusions or routing rules against nearby siblings such as contract_info, read_contract, or storage_slot. The agent must infer that this is the pre-step before reading a contract's real ABI.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crypto, web, finance and app data tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?