Skip to main content
Glama

Fast EVM Address Safety Ping

ingravity_fastPingAddressSafety
Read-onlyIdempotent

Checks an EVM address for SAFE/DANGER status across five chains via a read-only x402 v2 API, helping gate contracts, tokens, or spenders before interaction.

Instructions

Queries the Ingravity x402 v2 API (/api/v1/fast-ping) for a binary SAFE/DANGER address gate across 5 EVM chains ($0.01 USDC flat on Base Mainnet). Strictly read-only.

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...).
chainIdNoTarget EVM chain ID (8453 Base default, 42161 Arbitrum, 10 Optimism, 137 Polygon, 1 Ethereum).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive. The description adds real value beyond them: the x402 v2 endpoint, a flat $0.01 USDC cost on Base Mainnet (a paid-call implication the agent must know), and that the result is a binary SAFE/DANGER gate. It does not explain thresholds for DANGER or failure modes, but the cost and endpoint disclosure is substantive.

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?

One front-loaded sentence packed with endpoint, output shape, chain coverage, cost, and safety posture, with no filler. It is slightly dense with parentheticals, but every clause carries information an agent needs.

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?

With only two parameters, rich annotations, and no output schema, the description covers the essentials: where it calls, what it returns (binary SAFE/DANGER), which chains, and the payment cost. Minor gaps remain around payment failure behavior and what triggers DANGER, but nothing critical for correct invocation is missing.

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 100%, and the schema already documents the 42-character address format and the chainId enum with names and default. The description only restates '5 EVM chains' and adds no format, validation, or per-chain behavioral nuance beyond the schema, so baseline 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?

The description states a specific verb and resource (queries /api/v1/fast-ping for a binary SAFE/DANGER address gate) and scopes it to 5 EVM chains. This is clearly distinguishable from sibling tools like decodeEvmCalldataSelector, auditSolidityContract, or scanTokenRugpullAndHoneypot, which operate on calldata, source, or token contracts rather than a fast address-level gate.

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 'fast' and 'binary SAFE/DANGER gate' imply a quick pre-check use case, but the description never says when to prefer this over siblings such as scanTokenRugpullAndHoneypot or inspectEvmTransactionFirewall, nor any exclusions. Usage is inferable but not stated.

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