Skip to main content
Glama

APEX DeFi, DefiLlama & 8-Chain EVM Intel

Contract audit

contract_audit
Read-onlyIdempotent

Full smart contract security audit across 8 EVM chains (ethereum, base, arbitrum, optimism, polygon, bsc, arc, robinhood): bytecode disassembly, EIP-1967/1167 proxy inspection, admin powers, Sourcify source static analysis, and risk verdict. $0.05 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesethereum, base, arbitrum, optimism, polygon, bsc, arc or robinhood
addressYescontract address (0x...)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: pricing ($0.05 per call), accepted payment rails (x402 USDC on Arc/Base/Solana or XNT on X1), and the two-call handshake required before payment. The readOnlyHint is not contradicted — the tool reads chain state and the payment is a separate handshake, which the description makes explicit.

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-loads the capability and scope, then the payment mechanics in one dense but well-ordered sentence. Slight redundancy: the eight chain names are repeated verbatim in the `chain` schema description, which is wasted space.

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?

No output schema exists, yet the description names the deliverable ('risk verdict') and the analyses behind it, and it fully covers the payment workflow. Return format details (report structure, pagination) are absent but not critical for correct invocation.

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%, so baseline would be 3, but the description goes further by explaining the purpose of the optional `payment` parameter within the two-step flow (first call for terms, second with a signed payload), which the schema alone does not convey. Chain and address are already fully documented in the schema, so no credit lost there.

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 and resource ('Full smart contract security audit') plus scope (8 named EVM chains) and the concrete analyses performed: bytecode disassembly, EIP-1967/1167 proxy inspection, admin powers, Sourcify static analysis, risk verdict. An agent can distinguish this from sibling checks like arc_contract_check or contract_flags without opening the schema.

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?

Gives explicit procedural guidance for the paid flow: call once without `payment` to get terms, sign with your own wallet, call again with `payment` to complete the purchase. It does not, however, say when to prefer this over sibling audit/check tools, so selection guidance is implied rather than stated.

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.