Skip to main content
Glama

Ingravity Autonomous EVM Security & DeFi Guard (x402 v2)

Token Honeypot, Rugpull & EVM Address Safety Check (Fast-Ping)

ingravity_fastPingAddressSafety
Read-onlyIdempotent

Checks whether a single EVM address (0x...) is SAFE, DANGER, or UNKNOWN_UNVERIFIED_RPC across five chains (chainId: 8453 Base default, 42161 Arbitrum, 10 Optimism, 137 Polygon, 1 Ethereum; unknown IDs fall back to 8453). Strictly read-only, returning only a binary status and PROCEED/ABORT/CAUTION action with zero forensic leakage. Costs $0.01 USDC flat on Base via x402 v2; unpaid calls return isError: true with the payment challenge. Best for <=$0.05 bot budgets; escalate to ingravity_scanTokenRugpullAndHoneypot for tokens or ingravity_inspectEvmTransactionFirewall before signing calldata.

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": {
      "address": "<address>"
    },
    "name": "ingravity_fastPingAddressSafety"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes42-character EVM contract, token, or spender address (0x...) across Base, Arbitrum, Optimism, Polygon, or Ethereum.
chainIdNoTarget EVM chain ID: 8453 (Base), 42161 (Arbitrum), 10 (Optimism), 137 (Polygon), or 1 (Ethereum). Unsupported values fall back to 8453.

Output Schema

NameRequiredDescriptionDefault
actionYesRecommended execution directive.
isSafeYesTrue only when address passed deterministic and live RPC checks.
signalYesTraffic-light risk indicator.
statusYesBinary address risk classification.
chainIdYesResolved EVM chain ID used for evaluation.
settledYesWhether x402 USDC payment settled cleanly.
verdictYesMirror of status for downstream routing.
targetAddressYesNormalized lowercase address evaluated.
forensicDetailsYesFixed sentinel ('LOCKED_IN_FAST_PING_TIER'); upgrade to tx-firewall for forensics.
upgradeForFullForensicsNoUpgrade paths for calldata or token forensics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly/idempotent/non-destructive) by disclosing a flat $0.01 USDC x402 v2 cost, that unpaid calls return isError: true with a payment challenge, that output is only a binary status plus PROCEED/ABORT/CAUTION with no forensic detail, and that unknown chain IDs silently fall back to 8453. These are exactly the operational facts an agent needs before calling a paid endpoint.

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?

Dense and front-loaded: the core verdict vocabulary comes first, then chain scope, then cost, then escalation paths. Almost every clause carries information, though the single run-on paragraph and the undefined phrase 'zero forensic leakage' cost it a point.

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

Completeness4/5

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

For a 2-parameter read-only paid endpoint with a declared output schema and full annotation coverage, the description covers cost, payment failure mode, chain scope, and sibling escalation. Only the vague 'zero forensic leakage' claim and absent rate-limit guidance keep it from a 5.

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% and the schema already documents the address format, the chainId enum, and the 8453 fallback rule, so the description largely restates structured data. It adds no new detail on address casing, checksum handling, or EOA-vs-contract behavior, so the baseline of 3 applies.

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 (checks whether a single EVM address is SAFE/DANGER/UNKNOWN_UNVERIFIED_RPC) and enumerates the exact supported chains and default. It also names the sibling tools it is not, so an agent can distinguish it from ingravity_scanTokenRugpullAndHoneypot without opening either 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?

Explicit routing guidance: 'Best for <=$0.05 bot budgets; escalate to ingravity_scanTokenRugpullAndHoneypot for tokens or ingravity_inspectEvmTransactionFirewall before signing calldata.' It gives both the condition to use this tool and the concrete alternatives for adjacent jobs.

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.