Skip to main content
Glama

24-Vector Solidity Contract Auditor

ingravity_auditSolidityContract
Read-onlyIdempotent

Runs deterministic 24-vector static audits on Solidity source code and filters noise through four gates so developers can identify smart contract risks before deployment.

Instructions

Calls /api/v1/audit-solidity ($0.85 Full / $0.35 Essential USDC via x402 v2) for a deterministic 24-vector Solidity static audit with 4-gate anti-noise filtering.

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.
tierNoFULL
chainIdNo
contractNameNoContract.sol
ownerTreasuryNoOptional owner/multisig recipient address.
contractAddressNoOptional deployed contract address for live TVL check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description does add real value beyond that by disclosing that the call is paid ($0.85 Full / $0.35 Essential USDC via x402 v2), which is critical cost/authorization context, but it says nothing about what a result contains, failure modes, or 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 that front-loads the endpoint, then pricing, then audit substance. Every clause carries information; the only cost is that the parameter mapping stays implicit.

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

Completeness3/5

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

For a six-parameter, paid, no-output-schema tool, the description covers cost and audit nature but omits what the audit returns, what the optional contractAddress/ownerTreasury are for, and the chainId default. Adequate to select the tool, incomplete for invoking it precisely with the optional parameters.

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 coverage is 50% and the description names no parameters explicitly except by implication: the '$0.85 Full / $0.35 Essential' pricing gives the tier enum actual meaning, which the schema does not. That pricing is genuinely useful, but chainId, contractName, ownerTreasury and contractAddress get no explanation or defaults guidance from the description.

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?

The description names a specific verb and resource ('24-vector Solidity static audit') and adds distinguishing traits: deterministic, 4-gate anti-noise filtering, and the backing endpoint /api/v1/audit-solidity. It is clearly separable from siblings like scanTokenRugpullAndHoneypot or simulateDeepExploitAndWhitehatBounty, though it never explicitly contrasts itself with them.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no pointer to alternatives such as the rugpull/honeypot scanner for deployed tokens versus source-level auditing. The agent must infer from 'static audit' that the source code is already in hand.

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