Skip to main content
Glama

check_sanctions__screen

Screen a name against US OFAC + UK OFSI + EU consolidated sanctions lists (fuzzy match, scored). 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/screen

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

Input Schema

NameRequiredDescriptionDefault
nameNo
limitNo
thresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "type": "number"
      +}
  2. Changed6 schema fields changed
    • removedInput schema / properties / address
      Removed value: -{
      -  "description": "Crypto wallet address to screen",
      -  "type": "string"
      -}
    • 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 / description
      Removed value: -"Match similarity threshold, default 0.85"
    • removedInput schema / properties / threshold / maximum
      Removed value: -1
    • removedInput schema / properties / threshold / minimum
      Removed value: -0.5
  3. Changed7 schema fields changed
    • addedInput schema / properties / address
      Added value: +{
      +  "description": "Crypto wallet address to screen",
      +  "type": "string"
      +}
    • addedInput schema / properties / domain
      Added value: +{
      +  "description": "Domain to look up RDAP registration facts",
      +  "type": "string"
      +}
    • removedInput schema / properties / limit
      Removed value: -{
      -  "type": "number"
      -}
    • addedInput schema / properties / name / description
      Added value: +"Company or entity name to screen"
    • addedInput schema / properties / threshold / description
      Added value: +"Match similarity threshold, default 0.85"
    • addedInput schema / properties / threshold / maximum
      Added value: +1
    • addedInput schema / properties / threshold / minimum
      Added value: +0.5
  4. Changed5 schema fields changed
    • removedInput schema / properties / limit / description
      Removed value: -"Maximum matches, default 5."
    • changedInput schema / properties / limit / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / name / description
      Removed value: -"Entity or person name to screen; q is an alias."
    • removedInput schema / properties / threshold / description
      Removed value: -"Minimum fuzzy score 0-1, default 0.85."
    • removedInput schema / required
      Removed value: -[
      -  "name"
      -]
  5. Changed4 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Maximum matches, default 5.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / name / description
      Added value: +"Entity or person name to screen; q is an alias."
    • addedInput schema / properties / threshold
      Added value: +{
      +  "description": "Minimum fuzzy score 0-1, default 0.85.",
      +  "type": "number"
      +}
    • addedInput schema / required
      Added value: +[
      +  "name"
      +]
  6. Changed4 schema fields changed
    • removedInput schema / properties / limit
      Removed value: -{
      -  "description": "Max results returned, default 5.",
      -  "type": "integer"
      -}
    • removedInput schema / properties / name / description
      Removed value: -"Name to screen (alias: q)."
    • removedInput schema / properties / threshold
      Removed value: -{
      -  "description": "Fuzzy match threshold 0.5-1.0, default 0.85.",
      -  "type": "number"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "name"
      -]
  7. Changed5 schema fields changed
    • removedInput schema / properties / address
      Removed value: -{
      -  "description": "Crypto wallet address to screen.",
      -  "type": "string"
      -}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Max results returned, default 5.",
      +  "type": "integer"
      +}
    • 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 (alias: q)."
    • 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."
    • addedInput schema / required
      Added value: +[
      +  "name"
      +]
  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

A3.5/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 load and does well: it discloses the matching behavior (fuzzy, scored), the metered price ($0.01/call in USDC on Base), the payment channel (x402 in params._meta['x402/payment']), and the transport endpoint. It omits rate limits, what a no-match or error response looks like, and whether payment is charged on failed screens.

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?

Two tight sentences, front-loaded with capability and sourcing before cost and transport details. No filler words and nothing repeated from the schema.

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?

Payment, endpoint, and list coverage are complete, but with no output schema the definition should sketch the return shape (match verdict, score, matched entity) and it does not. Undocumented limit/threshold parameters remain a real gap for a tool with three inputs.

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 description coverage is 0% across three parameters, so the description must compensate. It only implies 'name' semantically; 'limit' and 'threshold' are never explained, even though 'fuzzy match, scored' is clearly the concept threshold controls. An agent cannot tell what units threshold uses or what limit caps.

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 ('Screen a name') plus the exact list coverage (US OFAC, UK OFSI, EU consolidated) and matching method (fuzzy, scored). The phrase 'a name' implicitly separates it from the address/seller/token siblings, though those alternatives are never named.

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 scope makes the use case obvious (person/entity name screening), but there is no explicit guidance on when to prefer this over check_sanctions__address, check_sanctions__entities, or check_sanctions__verdict, and no note on prerequisites or follow-up steps.

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