Skip to main content
Glama

check_sanctions__verdict

One-call combined exposure verdict for a name and/or wallet. 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/verdict

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__verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / address
      Removed value: -{
      -  "type": "string"
      -}
  2. 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 / description
      Removed value: -"Company or entity name to screen"
    • removedInput schema / properties / threshold
      Removed value: -{
      -  "description": "Match similarity threshold, default 0.85",
      -  "maximum": 1,
      -  "minimum": 0.5,
      -  "type": "number"
      -}
  3. 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 / description
      Added value: +"Company or entity name to screen"
    • addedInput schema / properties / threshold
      Added value: +{
      +  "description": "Match similarity threshold, default 0.85",
      +  "maximum": 1,
      +  "minimum": 0.5,
      +  "type": "number"
      +}
  4. Changed2 schema fields changed
    • removedInput schema / properties / address / description
      Removed value: -"Counterparty wallet address."
    • removedInput schema / properties / name / description
      Removed value: -"Counterparty name to screen."
  5. Changed2 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Counterparty wallet address."
    • addedInput schema / properties / name / description
      Added value: +"Counterparty name to screen."
  6. Changed3 schema fields changed
    • removedInput schema / properties / address / description
      Removed value: -"Wallet address to screen (optional if name given)."
    • removedInput schema / properties / name / description
      Removed value: -"Name to screen (optional if address given)."
    • removedInput schema / properties / threshold
      Removed value: -{
      -  "description": "Fuzzy match threshold 0.5-1.0, default 0.85.",
      -  "type": "number"
      -}
  7. Changed3 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"Crypto wallet address to screen."New value: +"Wallet address to screen (optional if name given)."
    • changedInput schema / properties / name / description
      Previous value: -"Counterparty or company name to screen against OFAC, UK OFSI and EU lists."New value: +"Name to screen (optional if address given)."
    • changedInput schema / properties / threshold / description
      Previous value: -"Fuzzy match threshold 0.5-1.0 (default 0.85)."New value: +"Fuzzy match threshold 0.5-1.0, default 0.85."
  8. 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"
      -]
  9. First observed

TDQS

B3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does usefully disclose operational behavior absent from structured data: the $0.01 per-call price, USDC on Base (eip155:8453), and the x402 payment location in params._meta. However, it says nothing about what a "verdict" contains, whether payment failure blocks the call, or any rate limits, leaving significant behavioral gaps.

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?

The definition is short and front-loads the purpose before cost and transport details. The endpoint line is arguably redundant for an MCP caller but is compact and potentially useful for x402 payment construction; little of the text is wasted.

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 one-parameter tool with no output schema, the payment mechanics are well covered, but because no return schema exists the description should describe what the verdict looks like (fields, possible outcomes). The advertised "wallet" input that the schema does not support is also left unresolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single `name` parameter, so the description must compensate. It says the verdict is for "a name and/or wallet", but the schema exposes only `name` with no wallet property, creating a mismatch that could lead an agent to expect wallet input that the schema cannot accept. It adds no format guidance for the name itself.

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?

"One-call combined exposure verdict for a name and/or wallet" states a specific verb (produce a combined exposure verdict) and resource (sanctions exposure), and the word "combined" hints at the difference from address-only or screen siblings. It stops short of naming which sibling to use instead, so an agent must infer the distinction rather than read it.

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

Usage Guidelines2/5

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

The phrase "One-call combined" implies this is the single-call option for getting a verdict on multiple identifiers at once, but there is no explicit when-to-use, when-not-to-use, or named alternative among check_sanctions__address, check_sanctions__screen, or check_sanctions__bundle. An agent must guess whether to call this or the per-identifier tools.

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