Skip to main content
Glama

Pre-Flight EVM Transaction Firewall

ingravity_inspectEvmTransactionFirewall
Read-onlyIdempotent

Submits EVM transaction calldata to a live firewall for 5-chain RPC bytecode and EIP-1967/1167 proxy inspection, drainer interception, and unsigned revocation bundles.

Instructions

Submits transaction calldata to /api/v1/tx-firewall ($0.10 USDC on Base via x402 v2) for live 5-EVM RPC bytecode & EIP-1967/1167 proxy inspection, drainer interception, and unsigned EIP-5792 revocation bundles.

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": {
      "to": "<to>"
    },
    "name": "ingravity_inspectEvmTransactionFirewall"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget contract, token, or recipient address (0x...).
dataNoHexadecimal transaction calldata (0x...).0x
fromNoOptional signer wallet address (0x...).
valueNoOptional native wei value as decimal string.0
chainIdNo
ticketIdNoOptional ZK-EC exposure ticket ID.
capitalAtRiskUsdNoOptional protected capital value in USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/destructive=false and idempotent, so safety is covered, and the description adds genuinely new facts beyond them: a per-call price of $0.10 USDC on Base via x402 v2, that the inspection is live against 5 EVM RPCs, and that unsigned EIP-5792 revocation bundles are produced. The payment cost is exactly the kind of side-effect disclosure annotations cannot express. It stops short of 5 because it does not say what happens on firewall interception or what the response contains.

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 action and endpoint, then lists the three capabilities. Every clause carries information, though the endpoint path and x402 version are implementation detail that crowds out return-value information. No wasted framing or repetition.

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 7-parameter inspection tool with no output schema, the description never indicates what the agent gets back, for example a verdict, risk flags, detected drainer, or the revocation bundle format, nor what happens when the firewall blocks a transaction. The cost and capability disclosures are helpful, but a caller cannot predict the result shape or how to act on it.

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 86%, so the schema already documents to, data, from, value, chainId, and ticketId/ capitalAtRiskUsd. The description adds no interpretation of the two least obvious parameters (ticketId, capitalAtRiskUsd) and does not explain how chainId drives the '5-EVM' scope. This is the expected baseline with high coverage, but no added value.

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 and resource: submitting calldata to a tx-firewall endpoint for RPC bytecode/proxy inspection, drainer interception, and revocation bundle generation. The scope (pre-flight check before signing, 5 EVMs) is clear. It does not explicitly distinguish itself from siblings like ingravity_decodeEvmCalldataSelector or ingravity_scanTokenRugpullAndHoneypot, which is the only thing keeping it below 5.

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?

The word 'Pre-Flight' in the title and 'Submits transaction calldata ... for live inspection' imply the use case is checking a transaction before signing. However, there is no explicit when-to-use statement, no when-not-to-use exclusions, and no named alternative for plain calldata decoding or token rugpull scanning. Usage must be inferred.

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