Skip to main content
Glama
Sign In

x402-solana

by io.github.digitalweb33333-creator
OverviewDiscussionsAdmin

sanctions_screen

Screen a name against the official EU consolidated sanctions list (FISMA) for anti-money-laundering (AML) and watchlist checks — returns matches with a similarity score and context (EU reference, type, programme), not a binary yes/no. Price: $0.05 per call (x402 payment, USDC on Base mainnet).

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

Input Schema

NameRequiredDescriptionDefault
nameYesName to screen (person or entity), e.g. 'Saddam Hussein'
typeNoOptional: 'person' or 'enterprise'
limitNoMax matches [1-50], e.g. 10
thresholdNoMin similarity 0-1 to report a match (default 0.7)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description discloses key behavioral traits: it returns a similarity score and context rather than a binary answer, and it notes a $0.05 per-call fee and payment method. This goes beyond the tool name, though it does not detail authentication or rate limits.

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?

The description is a single, dense sentence that front-loads the core purpose and then adds output and cost details—no filler or repetition.

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?

The description covers purpose, output nature, and cost, which is sufficient for an agent to select and invoke the tool. It lacks explicit return formatting details, but since there is no output schema, the description gives a reasonable expectation of what the response contains.

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?

All four parameters are fully described in the schema (100% coverage), so the baseline is 3. The description does not add parameter-specific details beyond what the schema already provides.

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 clearly states the tool screens a name against the official EU consolidated sanctions list (FISMA) for AML/watchlist checks, using a specific verb ('screen') and resource. It also distinguishes from sibling tools that focus on agent ranks, crypto tokens, and Solana checks.

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?

The description implies use for AML and watchlist screening but does not explicitly mention when to avoid this tool or name alternatives. It provides context ('anti-money-laundering and watchlist checks') but no exclusions or comparison with sibling tools.

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

All x402-solana toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources