Skip to main content
Glama

Base Agent Due-Diligence Kit

Contract X-Ray ($0.010)

contract_xray
Read-onlyIdempotent

Token / smart-contract safety check before you buy, approve or send: rug-pull and honeypot risk signals read from live bytecode and storage. Can the owner mint, blacklist/freeze, pause, seize, change buy/sell tax, toggle trading or upgrade the code? Owner type (EOA / Safe multisig / timelock / renounced), proxy implementation, Sourcify verification, 0-100 risk score with flags. Base, Ethereum, Arbitrum, Optimism, Polygon; pay USDC on Base. Bytecode heuristics, not a full audit. PAID: $0.010 per call in USDC on Base via x402, or use a 0.25 USDC transfer pass (pay_tx). See payment_options. By Nova.

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

Input Schema

NameRequiredDescriptionDefault
chainNoChain to scan (default base). Payment is always USDC on Base.
pay_txNoOptional, for the plain-transfer option (no x402 needed): hash of a USDC transfer of >= 0.25 USDC to this server's receiving address (get it from the payment_options tool). One transfer unlocks every paid tool for 24h.
addressYesContract address to scan
pay_chainNoChain of pay_tx (default: inferred; 0x hash = base, base58 signature = solana)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial context they cannot convey: cost ($0.010 USDC on Base via x402), an alternate plain-transfer pass of 0.25 USDC that unlocks every paid tool for 24h, which chains accept payment versus which are scanned, and the explicit limitation that results are bytecode heuristics rather than a full audit. It also previews the returned artifacts (0-100 risk score with flags, owner type, proxy implementation, Sourcify verification). No annotation conflict: scanning is genuinely read-only, with payment handled out of band.

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?

Purpose is front-loaded in the first clause, followed by capability detail, then scope, caveat, and payment terms in a logical order. Sentences are dense but each carries information an agent needs. The fragment style ('Owner type (EOA / Safe multisig / timelock / renounced), proxy implementation, Sourcify verification...') is slightly run-on, keeping it from a top score.

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?

There is no output schema, so the description carries the burden of describing returns, and it does: risk flags, owner classification, proxy implementation, verification status, and a 0-100 score. Between the return preview, the audited-vector list, the chain scope, and the payment mechanics, an agent has everything needed to decide and call 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 description coverage is 100% and all four parameters are individually documented, including enums for chain and pay_chain, so the schema already does the heavy lifting. The description reinforces that 'Payment is always USDC on Base' regardless of scanned chain, which clarifies how chain and pay_chain relate, but adds little beyond the schema's own text. Baseline 3 applies.

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 states a specific verb and resource: a token/smart-contract safety check that reads rug-pull and honeypot risk signals from live bytecode and storage. It enumerates exactly what is inspected (mint, blacklist/freeze, pause, seize, tax changes, trading toggle, upgrade) and which chains it covers. It does not name a sibling to contrast with, and the presence of a near-identical 'contract_xray_peek' alternative is only obliquely implied by the 'PAID' marker, so it falls short of full sibling differentiation.

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?

'before you buy, approve or send' gives a clear decision context for invoking the tool, and 'Bytecode heuristics, not a full audit' sets an expectation boundary. Payment routing to payment_options is also spelled out. However, there are no explicit when-not-to-use conditions and no direct pointer to the cheaper preview sibling for a quick look, so the guidance stops short of naming alternatives.

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