Skip to main content
Glama

Multi-Contract DeFi Protocol Auditor

ingravity_generateMultiContractProtocolDossier
Read-onlyIdempotent

Audits 1–20 interdependent Solidity contracts for cross-contract reentrancy and ERC-4626/oracle invariant issues, producing a protocol risk dossier.

Instructions

Calls /api/v1/protocol-dossier ($12.00 Full / $3.50 Essential USDC via x402 v2) to audit 1-20 interdependent Solidity contracts for cross-contract reentrancy and ERC-4626/oracle invariants.

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
tierNoFULL
chainIdNo
contractsYes
protocolNameNoDeFi Protocol
tvlTargetUsdNo
ownerTreasuryNo
contractAddressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely non-obvious context: it is a paid x402 v2 endpoint with concrete prices ($12.00 Full / $3.50 Essential USDC) and hard scope limits (1-20 contracts). It still says nothing about what happens on payment failure, rate limits, or processing latency.

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?

A single dense sentence with no filler; every clause (endpoint, price, contract count, analysis targets) carries information. The ordering is slightly off — it leads with the internal API path and price before the purpose, which is less front-loaded than ideal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and the description never characterizes what a 'dossier' contains, so an agent cannot anticipate the return value of a $12 call. Combined with zero parameter documentation for five optional inputs, the definition is thin for a 7-parameter paid audit tool, even though its scope and cost statements are accurate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 7 parameters, so the description must carry the load and it does not. Only the tier enum gets indirect meaning through the price mapping, and the 1-20 bound merely restates minItems/maxItems already in the schema. chainId, protocolName, tvlTargetUsd, ownerTreasury and contractAddress receive no explanation at all, including which of them affect the audit output.

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?

States a specific verb (audit) and resource (1-20 interdependent Solidity contracts) plus the exact analysis classes (cross-contract reentrancy, ERC-4626/oracle invariants). The 'interdependent'/'cross-contract' framing implicitly separates it from the single-contract sibling, but it never names that sibling, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

Usage is only implied by the object-count scope (1-20 interdependent contracts) — an agent can guess this is the multi-contract path versus ingravity_auditSolidityContract, but no explicit when-to-use/when-not or alternative is stated. No prerequisites, prerequisites for payment, or failure conditions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.