Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

multichain_wallet_aml_risk_screener

Read-onlyIdempotent

Multi-Chain Wallet Portfolio & AML Risk Screener: Real-time structured data extraction feed for Multi-Chain Wallet Portfolio & AML Risk Screener.

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

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds only the vague claim of "real-time" data, without saying which chains are covered, whether a wallet address is required for meaningful results, latency/freshness limits, or what the feed returns.

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

Conciseness2/5

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

It is short, but the second half is a pure duplicate of the title, so no sentence earns its place beyond repeating the tool name. Nothing is front-loaded as actionable context for invocation.

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

Completeness2/5

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

A wallet AML screener implies substantial output (risk scores, sanctions matches, chain-specific holdings), and with no output schema the description should have described the return surface and required inputs. Notably zero required parameters are declared, and the description does not clarify how the screen is targeted.

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?

The tool has a single parameter (maxResults) with 100% schema description coverage, so the schema already fully defines it and the baseline of 3 applies. The description contributes nothing about result volume, pagination, or truncation behavior beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the title verbatim ("Real-time structured data extraction feed for Multi-Chain Wallet Portfolio & AML Risk Screener") without a concrete verb or resource action. "Structured data extraction feed" is generic filler that does not tell an agent what it actually retrieves or how a wallet portfolio differs from an AML risk verdict.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisite, and no named alternative, even though siblings like global_sanctions_pep_gleif_kyb_screener and dex_token_scanner_security_auditor occupy adjacent screening territory. The agent is left to infer selection entirely from the name.

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