Skip to main content
Glama

Base Agent Due-Diligence Kit

Solidity Red-Flag Scan ($0.020)

solidity_red_flag_scan
Read-onlyIdempotent

Before you buy, approve or deposit: scans a contract's verified Solidity source (Sourcify; follows proxies to the implementation) for red flags with file, line and reason: blocklists, unbounded fee setters, owner balance edits, trading switches, owner mint, pause, upgradeability, arbitrary transferFrom (approval drain), arbitrary delegatecall, unprotected initializer, reentrancy order, unchecked calls, tx.origin auth, signature replay, weak randomness. Heuristic, not an audit. Unverified contracts are not charged. PAID: $0.020 per call in USDC on Base via x402, or use a 0.25 USDC transfer pass (pay_tx). See payment_options. By Lao K.

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

Input Schema

NameRequiredDescriptionDefault
chainNoChain of the contract (default base). Payment is always USDC on Base.
followNo1 (default) = if it is a proxy, also scan the implementation
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 (verified on Sourcify)
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.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses that unverified contracts are not charged, that heuristics can miss issues, that proxies are followed to the implementation, and the full payment mechanics ($0.020 USDC on Base via x402, or a 0.25 USDC transfer pass unlocking 24h). That is substantive context the annotations cannot convey.

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?

It is front-loaded with the decision context ('Before you buy, approve or deposit') before the mechanics. The 20-item enumeration of red-flag categories is a long unpunctuated run, but each entry is a discrete detection capability rather than 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?

For a paid, heuristic scanner with no output schema, the description covers the input contract type (verified Sourcify source), detection scope, result shape, cost and payment routes, and a pointer to payment_options. An agent has everything needed to decide and invoke.

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 explains that proxies are followed to the implementation (the 'follow' parameter), and that payment is USDC on Base regardless of the scanned chain (clarifying 'chain' vs 'pay_chain'). The pricing detail also contextualizes 'pay_tx'.

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?

A specific verb and resource are stated: it scans a contract's verified Solidity source (via Sourcify, following proxies) for enumerated red flags, and the response shape (file, line, reason) is named. The gaps lie in not naming a sibling such as solidity_scan_peek or contract_xray, so the agent must infer where this fits among the preview/peek tools.

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?

The opening phrase 'Before you buy, approve or deposit' gives an explicit trigger context for use, and 'Heuristic, not an audit' sets a clear boundary on what it is not. It stops short of naming the alternative tool an agent should pick for a free preview or a deeper audit.

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