Skip to main content
Glama

Check an EVM address against public risk feeds (paid, x402)

check_address

PAID: check a wallet address (EVM) against public risk feeds (OFAC, darklists, on-chain age): verdict, score, reasons. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply. Price: $0.0100 USDC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNo"base" or "ethereum", default "base".
addressNoAn EVM 0x... address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / required
      Removed value: -[
      -  "address"
      -]
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the paywall mechanics, supported payment chains, the exact price, and that unpaid calls return only a price rather than a verdict. The feedback endpoint note ('read daily; no individual reply') is unusual but informative. Missing are anything about latency, caching/freshness of the risk feeds, or what happens on partial payment failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The paid-usage facts are front-loaded behind the 'PAID:' marker, which is effective. However, the trailing 'Feedback: POST /feedback (free). Read daily; no individual reply' is tangential to invoking this tool and reads as compacted boilerplate, fragmenting an otherwise tight description.

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 two-parameter tool with no output schema, the description covers what comes back (verdict, score, reasons), what an unpaid call returns, and how to complete payment. An agent has enough to call it correctly on the first attempt; only freshness and error behavior are unstated.

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%: both 'address' (0x EVM address) and 'chain' (with its default) are already documented in the schema. The description adds no syntax, format, or validation meaning beyond that, so the baseline of 3 applies.

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 leads with a specific verb ('check'), a precisely scoped resource ('a wallet address (EVM)'), the data sources consulted (OFAC, darklists, on-chain age) and the return shape (verdict, score, reasons). The 'EVM wallet address' resource scope implicitly separates it from siblings like check_url or check_counterparty, though no sibling is named.

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

Usage Guidelines4/5

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

The workflow is explicit: call unpaid to get a price, pay via x402 in _meta['x402/payment'], then call again. That is strong operational guidance with a clear sequencing condition. It stops short of saying when to prefer this over check_counterparty or when a risk check is warranted at all.

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.

Resources