Skip to main content
Glama

Ingravity Autonomous EVM Security & DeFi Guard (x402 v2)

24-Vector Solidity Contract Auditor

ingravity_auditSolidityContract
Read-onlyIdempotent

Audits a single Solidity file (code, required; optional contractName) across 24 SWC/DeFi rules using a 4-gate filter that excludes dust rounding and trusted-admin paths. Read-only and never broadcasts transactions: optionally supply deployed contractAddress, chainId (default 8453), and ownerTreasury to check live TVL via RPC and generate unsigned EIP-5792/EOA Safe-Harbor rescue calldata (90%-95% to ownerTreasury). Set tier to FULL ($0.85 USDC, default) for findings or ESSENTIAL ($0.35 USDC) for score and counts; unpaid calls return isError: true, and CRITICAL/HIGH patches remain sealed under Anti-Bypass until 0.15% SLA or 5%-10% rescue settlement. Use for single contracts; use ingravity_generateMultiContractProtocolDossier for multi-file protocols.

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": {
      "code": "<code>"
    },
    "name": "ingravity_auditSolidityContract"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesRaw Solidity (.sol) smart contract source code to audit across 24 SWC/DeFi rules (non-empty string required).
tierNoBilling & output depth: FULL ($0.85 USDC) includes findings and Safe-Harbor calldata (subject to Anti-Bypass sealing on CRITICAL/HIGH until proportional settlement); ESSENTIAL ($0.35 USDC) returns score, grade, status, and severity counts only.FULL
chainIdNoEVM Chain ID used only when contractAddress is supplied for live TVL verification (8453 Base, 42161 Arbitrum, 10 Optimism, 137 Polygon, 1 Ethereum; unknown falls back to 8453).
contractNameNoOptional contract identifier or filename echoed in the report.Contract.sol
ownerTreasuryNoOptional protocol owner/multisig recipient (0x...) designated to receive 90%-95% of rescued capital in generated unsigned calldata.
contractAddressNoOptional deployed EVM contract address (0x...) on chainId to verify live TVL via RPC and generate unsigned Safe-Harbor rescue calldata.

Output Schema

NameRequiredDescriptionDefault
locYesSource lines of code analyzed.
gradeYesLetter grade derived from securityScore.
actionYesDeployment gate directive.
signalYesTraffic-light severity indicator.
statusYesOverall readiness verdict.
chainIdYesResolved EVM chain ID.
settledYesWhether x402 USDC payment settled cleanly.
summaryYesFinding counts grouped by severity.
findingsNoPer-finding details with line coordinates and fix guidance (FULL tier only; CRITICAL/HIGH coordinates sealed until proportional settlement when applicable).
contractNameYesAudited contract label.
securityScoreYesDeterministic security score from 0 to 100.
verifiedOnChainTvlUsdYesLive on-chain TVL verified via RPC when contractAddress is supplied (0 otherwise).
savedCapitalEstimateUsdYesEstimated capital at risk or prevented exploit range.
capitalSalvageAndSafeHarborNoUnsigned Safe-Harbor rescue plan or optional pre-deploy circuit-breaker snippet (FULL tier only).
proportionalRescueCommissionPolicyNo0.15% Pre-Flight SLA and 5%-10% Safe-Harbor policy metadata (FULL tier only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior, but the description adds substantial context: no transaction broadcasting, optional RPC TVL verification, unsigned rescue calldata generation, pricing, unpaid-call failure behavior, and Anti-Bypass sealing for CRITICAL/HIGH patches.

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?

The description is front-loaded with purpose and contains no clearly wasted sentences. However, the middle sentence is dense with billing, RPC, calldata, and settlement clauses, which slightly reduces readability for an agent parsing the definition.

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 complex paid audit tool with optional live-chain verification and security gating, the description covers the critical behavior an agent needs before calling it. Since an output schema exists, it does not need to explain return values in detail.

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 all six parameters are already documented in the input schema. The description reinforces their roles and interconnections, such as chainId being used with contractAddress and ownerTreasury receiving 90%-95% of rescued capital, but it does not add much parameter meaning beyond what the schema already states.

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?

The description states a specific verb and resource: it audits a single Solidity file across 24 SWC/DeFi rules. It also explicitly distinguishes single-contract audits from multi-file protocol analysis by naming the sibling tool to use for the latter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to use this for single contracts and to use ingravity_generateMultiContractProtocolDossier for multi-file protocols. It also explains when optional live TVL checks apply and how FULL versus ESSENTIAL tier selection changes the request.

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.