Skip to main content
Glama

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

Contract ABI, verified contract: ABI and source

contract_abi
Read-only

The verified ABI of a smart contract on Ethereum, Base, Arbitrum, Optimism or Polygon from Sourcify's open verification repository: contract name, compiler, match quality, every function and event signature, the full ABI, and for proxies the implementation contract with its ABI. Optional source=true adds the main source file (up to 20,000 characters). Unverified contracts are an uncharged 422. Use before calling or decoding a contract. Example: address=0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48. 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": "contract_abi"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoethereum (default), base, arbitrum, optimism or polygon
sourceNotrue to include the main source file
addressYesContract 0x address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations: discloses per-call pricing ($0.01 via x402 USDC or card key, first 25 free, failed calls free), that unverified contracts return an uncharged 422, the 20,000-character cap on source, and that proxy lookups resolve the implementation. The note that repeats are charged is consistent with idempotentHint=false, and "reads or computes only and changes nothing" aligns with readOnlyHint=true.

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?

A single dense paragraph that front-loads what the tool returns, then layers usage, edge cases (422), an example, and pricing. Every sentence carries information an agent would otherwise have to guess; there is no filler.

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?

Despite having no output schema, the description enumerates the returned fields, the proxy behavior, the optional source payload and its size limit, the failure mode, and the billing model. Nothing material for correct invocation appears to be missing for a three-parameter read tool.

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 the baseline is 3, but the description adds real meaning: it clarifies the chain set and default behavior context and explains that source=true returns the main source file capped at 20,000 characters. It still adds nothing about the address parameter's validation or the loose string/number/boolean typing of source.

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?

Names a specific verb+resource (the verified ABI of a smart contract) and enumerates the payload: contract name, compiler, match quality, function/event signatures, full ABI, and proxy implementation ABI. It also scopes the supported chains, so an agent can distinguish it from sibling helpers like eth_is_contract or arb_proxy without opening a 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 an explicit trigger: "Use before calling or decoding a contract," plus a concrete example address. It does not name alternatives (e.g. existence-check or proxy-lookup siblings) or state when this tool is unnecessary, so routing is implied rather than fully prescribed.

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.