Skip to main content
Glama

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

Smart contract audit: security review of one contract in one call

audit_contract
Read-only

Smart contract audit in one call: send a verified contract address (Ethereum, Base, Arbitrum, Optimism, Polygon) or Solidity source and get, within a minute or two, findings by severity with function, line, exploit scenario and fix, the owner and upgrade keys read on chain, a score and a Markdown report. Automated (static checks plus AI reviewers), not a manual audit. Use before deploying, integrating with or buying into a contract. Price $1.00/call via x402 USDC or a card key (/credits); failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "audit_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoethereum (default), base, arbitrum, optimism or polygon; used with address
sourceNoSolidity or Vyper source code, or the compiler's standard JSON input, up to 300,000 characters; POST it in a JSON body when it is long. Send this or address
addressNoVerified contract 0x address (a proxy is followed to its implementation). Send this or source
contextNoOptional notes for the reviewers, up to 1,000 characters: what the contract is for or what worries you

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes well past the annotations: it discloses cost ($1.00/call via x402 USDC or card key), that failed calls are free, latency (a minute or two), and that repeats are charged — which directly explains the idempotentHint=false signal. It also sets expectations that this is automated static-plus-AI review rather than a manual audit, and confirms the read-only nature stated in annotations. Minor gap: no detail on pagination or behavior when neither address nor source is supplied, though nothing contradicts the 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?

Front-loads the core promise and output inventory, then layers usage, pricing and caveats in a compact block with no filler sentences. Dense but every clause carries operational information (cost, timing, automation caveat) that affects the call decision.

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?

With no output schema, the description fully covers what is returned, how long it takes, what it costs, and the automated-vs-manual limitation — everything an agent needs to decide and invoke correctly. Nothing material is missing for a four-optional-parameter, read-only audit call.

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%, so every parameter (chain, source, address, context) is already documented including defaults, size limits and the address-vs-source choice. The description restates the supported chains and the two input modes but adds no format or constraint detail beyond the schema, so the baseline of 3 applies.

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 ('Smart contract audit in one call') and enumerates the concrete deliverables: findings by severity with function, line, exploit scenario and fix, owner/upgrade keys, a score and a Markdown report. Combined with the accepted input modes (verified address on five named chains, or Solidity source), an agent can tell exactly what it gets back 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 a clear trigger ('Use before deploying, integrating with or buying into a contract') and scopes the unit of work to one contract, which implicitly separates it from broader package/pool audits. It does not, however, explicitly name or distinguish itself from the sibling contract_audit, so an agent must still guess between the two similarly named tools.

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.