Skip to main content
Glama

Crypto address risk (x402)

get_crypto_address_risk

Read-onlyIdempotent

Screen any wallet address for compliance and security risk in one call: sanctions/OFAC exposure, money-laundering, financial-crime, phishing, stealing/honeypot-related, darkweb, mixer and blacklist flags — fused into a CLEAR / CAUTION / HIGH_RISK verdict. The KYT / AML / wallet-risk read every payment, settlement, compliance, and trading agent should make before transacting with a counterparty. Live from GoPlus address security across Ethereum, Base, BSC, Polygon, Arbitrum, Optimism, Avalanche. $0.09/call, no API key, USDC over x402.

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": "get_crypto_address_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_paymentNoSigned x402 payment payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover readOnly, idempotent, and openWorld, but the description adds substantial context beyond them: the underlying data source (GoPlus), the nine supported chains, the paid-access model ($0.09/call, USDC over x402, no API key), and the three-tier verdict scale. Cost and payment mechanics are exactly the kind of operational detail annotations cannot convey.

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?

Front-loaded with the action and the verdict output, followed by use case, coverage, and pricing. Dense but nearly every clause carries information. It leans slightly promotional ('the read every payment... agent should make') which is unnecessary framing but not harmful.

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

Completeness5/5

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

For a one-parameter read tool with no output schema, the definition supplies the verdict taxonomy, risk categories, chain coverage, data provenance, and cost model — everything an agent needs to decide to call it and interpret the headline result. No material gap remains for this complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single x_payment parameter, so baseline would be 3. The description earns above baseline by explaining the x402/USDC payment model that the parameter exists to satisfy, giving the agent context for why the payload is required even though the parameter is technically optional.

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 ('Screen any wallet address') plus the exact output it produces ('CLEAR / CAUTION / HIGH_RISK verdict') and the risk categories covered. It is clearly distinguishable from sibling tools such as token_security_check (token-level) or wallet_portfolio (holdings) because it is address-level risk screening.

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?

Explicitly frames the use case: the KYT/AML read 'every payment, settlement, compliance, and trading agent should make before transacting with a counterparty.' That is clear when-to-use guidance. It does not, however, name alternative or complementary tools (e.g., pretrade_full_report) or state when this tool is unnecessary.

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