Skip to main content
Glama

Ingravity Autonomous EVM Security & DeFi Guard (x402 v2)

Multi-Contract DeFi Protocol Auditor

ingravity_generateMultiContractProtocolDossier
Read-onlyIdempotent

Audits 1-20 interdependent Solidity contracts (contracts array of {name, code}, required; optional protocolName and tvlTargetUsd=1000000) for cross-contract read-only reentrancy, centralization, and 6 ERC-4626/oracle invariants. Strictly read-only: pass optional contractAddress, chainId (8453 Base default, 42161, 10, 137, 1), and ownerTreasury to verify live RPC TVL and build unsigned EIP-5792/EOA Safe-Harbor rescue steps (90%-95% to ownerTreasury). Set tier to FULL ($12.00 USDC, default) for call-graph and findings or ESSENTIAL ($3.50 USDC) for score and counts; unpaid returns isError: true, empty contracts throws -32602, and CRITICAL/HIGH patches stay sealed until 0.15% SLA or 5%-10% rescue settlement. Use for multi-file protocols; use ingravity_auditSolidityContract for single files or ingravity_simulateDeepExploitAndWhitehatBounty without source.

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": {
      "contracts": "<contracts>"
    },
    "name": "ingravity_generateMultiContractProtocolDossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNoBilling & output depth: FULL ($12.00 USDC) returns callGraphEdges, per-contract findings, invariants, and Safe-Harbor rescue calldata (subject to Anti-Bypass sealing on CRITICAL/HIGH until proportional settlement); ESSENTIAL ($3.50 USDC) returns readiness score, grade, status, and severity counts only.FULL
chainIdNoEVM Chain ID used when optional contractAddress is supplied for live RPC liquidity lookup (8453 Base, 42161 Arbitrum, 10 Optimism, 137 Polygon, 1 Ethereum; unknown falls back to 8453).
contractsYesNon-empty array of Solidity contracts belonging to the protocol (1 to 20 {name, code} objects; additional items beyond 20 are ignored).
protocolNameNoDeFi protocol or project name echoed in executiveSummary.DeFi Protocol
tvlTargetUsdNoTarget or declared TVL in USD used for bug bounty reward calibration when live RPC TVL is absent or lower.
ownerTreasuryNoOptional protocol multisig/treasury recipient (0x...) designated to receive 90%-95% of rescued funds in unsigned Safe-Harbor calldata.
contractAddressNoOptional deployed EVM vault/pool address (0x...) on chainId for live RPC TVL verification and unsigned Safe-Harbor rescue bundle generation.

Output Schema

NameRequiredDescriptionDefault
gradeYesLetter grade derived from protocolSecurityScore.
actionYesProtocol deployment gate directive.
signalYesTraffic-light risk indicator.
chainIdYesResolved EVM chain ID.
settledYesWhether x402 USDC payment settled cleanly.
summaryYesAggregated finding severity totals and failed invariant count.
protocolNameYesEvaluated protocol name.
contractAuditsNoPer-contract security audits and findings (FULL tier only).
executiveSummaryNoConsolidated protocol score, LOC, centralizationRiskIndex, and readiness breakdown (FULL tier only).
deploymentReadinessYesLaunch readiness classification.
bugBountyCalibrationNoRecommended bounty reward schedule by severity calibrated to TVL (FULL tier only).
crossContractAnalysisNoCross-contract call graph, read-only reentrancy findings, admin privilege map, and invariant checks (FULL tier only).
protocolSecurityScoreYesWeighted multi-contract security score from 0 to 100.
verifiedOnChainTvlUsdYesLive on-chain TVL verified via RPC when contractAddress is supplied (0 otherwise).
capitalSalvageAndSafeHarborNoUnsigned Safe-Harbor rescue bundle or optional pre-deploy circuit breaker (FULL tier only).
proportionalRescueCommissionPolicyNo0.15% Pre-Flight SLA and 5%-10% Safe-Harbor settlement metadata (FULL tier only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/openWorldHint/idempotentHint and destructiveHint=false, and the description stays consistent with that ('Strictly read-only') while adding substantial context the annotations cannot: tier pricing, that unpaid calls return isError: true, that empty contracts throws -32602, and that CRITICAL/HIGH patches stay sealed until an SLA or rescue settlement. It also discloses that live RPC lookups occur only when contractAddress is supplied, which matters for an open-world tool.

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?

Core purpose and scope are front-loaded, and nearly every clause carries factual payload (limits, defaults, prices, error codes, sealing rule). It is a single very dense block, though, and the error/sealing/billing clauses could be separated for faster scanning; no sentence is pure 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?

An output schema exists, so return values need not be explained, and the description instead covers the things that would otherwise block a correct call: input limits, required vs optional fields, defaults, billing tiers, error behavior, and sealing. Nothing material for invoking this 7-parameter tool correctly is missing.

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 and the schema already documents every parameter. The description still adds value beyond it by linking tier to concrete billing and sealing consequences ($12 vs $3.50, what each returns), tying chainId to the live RPC path, and explaining the 90%-95% ownerTreasury split and tvlTargetUsd's role in reward calibration.

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 (audits 1-20 interdependent Solidity contracts) plus the exact risk classes covered (cross-contract read-only reentrancy, centralization, 6 ERC-4626/oracle invariants). It also names the siblings it is NOT for, so an agent can separate it from ingravity_auditSolidityContract and ingravity_simulateDeepExploitAndWhitehatBounty without opening any schema.

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?

Gives an explicit selection rule: 'Use for multi-file protocols; use ingravity_auditSolidityContract for single files or ingravity_simulateDeepExploitAndWhitehatBounty without source.' Both the when and the when-not are stated, along with the condition (source available, multiple files) that decides between them.

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.