Skip to main content
Glama

contract_check

Live check of any contract on Ethereum or Base before you interact with it: is it an upgradeable proxy (EIP-1967, beacon, ZeppelinOS), its current implementation, and whether upgrades and owner() are controlled by a single key, a Safe multisig (m-of-n) or a timelock. Adds the upgrade history when the contract is one this feed watches. Costs $0.005 (x402, USDC).

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": {
      "chain": "<chain>",
      "address": "<address>"
    },
    "name": "contract_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesChain: ethereum, base
addressYesContract address, 0x followed by 40 hex characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose two valuable traits: the check is live (not cached) and it costs $0.005 paid via x402 in USDC, which tells the agent payment will be required. It also scopes the upgrade history to contracts 'this feed watches'. It does not say whether the call is read-only or safe to repeat, nor whether the payment is per call. These gaps are material for a paid tool with no annotations.

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 sentences, both loaded: the first packs the scope, the detected proxy standards, and the control-type taxonomy; the second adds the scope limit and the price. No sentence is filler, and the core purpose is front-loaded.

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 two-parameter tool with no output schema, the description explains well what is returned: proxy type, implementation address, and who controls upgrades via a single key, a Safe multisig with m-of-n, or a timelock. It does not describe the result shape when the contract is not a proxy, but an agent has enough to call it correctly.

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?

Schema coverage is 100%, so the schema already documents chain and address. The description adds only the accepted chains (Ethereum or Base), which the schema's chain description already states, and nothing about the address format beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific action and resource: a live inspection of a contract for proxy patterns (EIP-1967, beacon, ZeppelinOS), current implementation, and control structure, with upgrade history appended. It is clear what the tool does, but it never names or contrasts itself with the sibling quick_check, so the agent must guess which check to run first.

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?

It gives a clear trigger: run this before you interact with a contract. It does not state when not to use it, nor how it relates to quick_check or the protocol_* siblings, so pre-interaction use is the only routing signal provided.

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