Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

screen_wallet_aml_risk

Read-onlyIdempotent

Screen EVM and Solana wallet addresses for AML risk by checking balances, transaction velocity, mixer and OFAC sanctions exposure, and returning a 0-100 risk score.

Instructions

Screen EVM and Solana wallet addresses for native asset balances, recent transaction velocity, tornado/mixer exposure, OFAC sanctions flags, and automated anti-money-laundering (AML) risk scores (0-100).

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": {
      "addresses": "<addresses>"
    },
    "name": "screen_wallet_aml_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainsNoBlockchain networks to inspect for the provided addresses.
addressesYesEVM (0x...) or Solana base58 wallet addresses to screen.
maxTransactionsNoMaximum number of recent transactions to inspect per wallet address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses the output dimensions (balances, velocity, mixer exposure, OFAC flags) and the 0-100 risk-score scale, which matters because there is no output schema. It does not cover latency, per-chain costs, or how to interpret the score thresholds.

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

Conciseness5/5

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

A single dense sentence with no filler, front-loaded with the verb and resource and followed by the concrete signals returned. Every clause carries information an agent needs to select the tool.

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 three-parameter read-only screening tool with no output schema, the description is nearly complete: it names the chains domain, the address types, and the five result signals including the score range. The remaining gap is operational guidance, such as chain-selection tradeoffs or what a given score implies, which is not stated anywhere.

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 all three parameters (chains, addresses, maxTransactions) are already documented in the schema, including defaults and bounds; the description adds nothing parameter-specific beyond noting EVM and Solana address formats, which the schema also states. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific verb (screen) and a specific resource (EVM and Solana wallet addresses), then enumerates exactly what is checked: balances, transaction velocity, mixer exposure, OFAC flags, and a 0-100 AML risk score. That enumeration also distinguishes it from the sibling 'screen_global_sanctions_and_kyb' tool, which screens entities rather than on-chain wallet addresses.

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?

Usage is only implied by the purpose statement; there is no explicit guidance about when to use this tool versus the sanctions/KYB sibling, no prerequisites, and no note about when a screen is worth running across multiple chains. An agent can infer the use case from the enumerated risk signals, but nothing is stated about exclusions or preferred alternatives.

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