Skip to main content
Glama

check_sanctions__address

Exact-match a crypto wallet address against OFAC digital-currency addresses. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/check-sanctions/address

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

Input Schema

NameRequiredDescriptionDefault
addressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / address / description
      Removed value: -"Crypto wallet address to screen"
    • removedInput schema / properties / domain
      Removed value: -{
      -  "description": "Domain to look up RDAP registration facts",
      -  "type": "string"
      -}
    • removedInput schema / properties / name
      Removed value: -{
      -  "description": "Company or entity name to screen",
      -  "type": "string"
      -}
    • removedInput schema / properties / threshold
      Removed value: -{
      -  "description": "Match similarity threshold, default 0.85",
      -  "maximum": 1,
      -  "minimum": 0.5,
      -  "type": "number"
      -}
  2. Changed4 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Crypto wallet address to screen"
    • addedInput schema / properties / domain
      Added value: +{
      +  "description": "Domain to look up RDAP registration facts",
      +  "type": "string"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Company or entity name to screen",
      +  "type": "string"
      +}
    • addedInput schema / properties / threshold
      Added value: +{
      +  "description": "Match similarity threshold, default 0.85",
      +  "maximum": 1,
      +  "minimum": 0.5,
      +  "type": "number"
      +}
  3. Changed2 schema fields changed
    • removedInput schema / properties / address / description
      Removed value: -"Wallet address to look up; addr is an alias."
    • removedInput schema / required
      Removed value: -[
      -  "address"
      -]
  4. Changed2 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Wallet address to look up; addr is an alias."
    • addedInput schema / required
      Added value: +[
      +  "address"
      +]
  5. Changed2 schema fields changed
    • removedInput schema / properties / address / description
      Removed value: -"Wallet address to screen (alias: addr)."
    • removedInput schema / required
      Removed value: -[
      -  "address"
      -]
  6. Changed4 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"Crypto wallet address to screen."New value: +"Wallet address to screen (alias: addr)."
    • removedInput schema / properties / name
      Removed value: -{
      -  "description": "Counterparty or company name to screen against OFAC, UK OFSI and EU lists.",
      -  "type": "string"
      -}
    • removedInput schema / properties / threshold
      Removed value: -{
      -  "description": "Fuzzy match threshold 0.5-1.0 (default 0.85).",
      -  "type": "number"
      -}
    • addedInput schema / required
      Added value: +[
      +  "address"
      +]
  7. Changed5 schema fields changed
    • addedInput schema / properties / address
      Added value: +{
      +  "description": "Crypto wallet address to screen.",
      +  "type": "string"
      +}
    • removedInput schema / properties / days
      Removed value: -{
      -  "description": "Look-back window in days (default 30, max 400).",
      -  "type": "number"
      -}
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Counterparty or company name to screen against OFAC, UK OFSI and EU lists.",
      +  "type": "string"
      +}
    • removedInput schema / properties / names
      Removed value: -{
      -  "description": "Pipe-separated counterparty names to re-screen, up to 50.",
      -  "type": "string"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "names"
      -]
  8. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses price ($0.01/call), currency and chain (USDC on Base, eip155:8453), the x402 payment requirement in params._meta['x402/payment'], the transport (HTTP GET) and the exact endpoint. What it omits is result behavior — what a hit versus a miss returns, and whether the match is chain-aware or list-wide.

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?

Three tight clauses with the core purpose front-loaded, followed by cost and transport details. Nothing is padded, though the pricing and endpoint segments are delivered as terse fragments that lean on the reader already knowing x402 conventions.

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

Completeness3/5

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

For a single-parameter tool with no annotations and no output schema, the description covers cost, payment mechanism and endpoint well. The significant remaining gap is return shape: with no output schema, an agent has no idea whether it gets a boolean, a match record, or a verdict, and the description does not say.

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 coverage is 0% for the single 'address' parameter, so the description must compensate. It tells the agent the parameter is a crypto wallet address, and it adds a second parameter not in the schema (params._meta['x402/payment']) with its purpose. It does not state that 'address' is effectively required or give expected format (hex/checksummed, which chain), leaving the empty schema's optional-looking required list unclarified.

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

Purpose4/5

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

States a specific verb and resource: 'Exact-match a crypto wallet address against OFAC digital-currency addresses.' The 'exact-match' qualifier meaningfully separates it from fuzzy screening siblings, but no sibling is named explicitly, so discrimination relies on the agent knowing what the others do.

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 implied by 'exact-match' (single, precise wallet address against the OFAC digital-currency list), which hints at when this is appropriate versus a broader screen or a batch call. There is no explicit when-to-use or when-not guidance, and no alternatives such as check_sanctions__screen or check_sanctions__batch are referenced.

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