Skip to main content
Glama

Wallet risk

wallet_risk
Read-onlyIdempotent

Use for a rule-based risk label on an EVM address before paying it: exact sanctions match (OFAC SDN, UK and EU), contract or plain account (Base, Ethereum), outgoing transactions. Returns the paid x402 request for your input (GET /wallet/risk, $0.01 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For an ERC-20 token use token_risk; for the sanctions match of many addresses (all screened lists) use sanctions_screening_batch; for one payee address before paying, including Solana, use check_payee. First call each day returns the data itself, free; later calls return the paid request.

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

Input Schema

NameRequiredDescriptionDefault
addressYesEVM address (0x + 40 hex); ENS names are not resolved here
request_keyNoIdempotency key, echoed back

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?

Annotations already declare readOnly/openWorld/idempotent, but the description adds the non-obvious economics and mechanics: $0.01 per call, bad input rejected before any charge, and the fact that later calls return an x402/MPP payment request rather than data (with the first call each day returning data free). That "you must then follow the returned URL with an x402 or MPP client" step is a behavior an agent could not recover from the annotations or schema, and it is not contradicted by readOnlyHint.

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?

Purpose and the pay-before-you-pay framing come first, then alternatives, which is the right order, and there is no filler. It loses a point because the returns story is split awkwardly across the opening ("Returns the paid x402 request") and the closing ("First call each day returns the data itself, free"), so an agent has to reconcile two statements about what it gets back.

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 no output schema, the description does the necessary work of naming the three label dimensions (sanctions match, account type, outgoing transactions) and the payment round-trip, plus error handling for invalid input. It stops short of describing what the returned x402 request or the label payload looks like, which leaves an agent slightly unprepared for the response, but the coverage is strong for a paid two-parameter screening tool.

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%, so the schema already documents the EVM address pattern, the no-ENS caveat, and the idempotency key. The description adds no syntax, format, or behavioral nuance about either parameter beyond restating the address concept, so this sits at the baseline rather than above it.

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?

"Use for a rule-based risk label on an EVM address before paying it" names a specific verb (label/assess) and resource (EVM address), then enumerates the label components: exact sanctions match against OFAC SDN/UK/EU, contract vs plain account on Base/Ethereum, and outgoing transactions. The scope is unmistakably narrower than token_risk, sanctions_screening_batch, or check_payee, all of which are named.

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?

It gives an explicit trigger (before paying an address) and then routes to three named alternatives with the distinguishing condition for each: token_risk for ERC-20 tokens, sanctions_screening_batch for many addresses across all screened lists, check_payee for one payee including Solana. Cost and the free-first-call-per-day behavior are stated up front, which is exactly the context an agent needs to choose between paid screening calls.

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