Skip to main content
Glama

check_sanctions__batch

Screen up to 25 pipe-separated names in one call. 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/batch

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

Input Schema

NameRequiredDescriptionDefault
namesNo
thresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / threshold
      Added value: +{
      +  "type": "number"
      +}
  2. Changed5 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
      Removed value: -{
      -  "description": "Company or entity name to screen",
      -  "type": "string"
      -}
    • addedInput schema / properties / names
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / threshold
      Removed value: -{
      -  "description": "Match similarity threshold, default 0.85",
      -  "maximum": 1,
      -  "minimum": 0.5,
      -  "type": "number"
      -}
  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"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Company or entity name to screen",
      +  "type": "string"
      +}
    • removedInput schema / properties / names
      Removed value: -{
      -  "type": "string"
      -}
    • 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. Changed3 schema fields changed
    • removedInput schema / properties / names / description
      Removed value: -"Pipe-separated names, max 50."
    • removedInput schema / properties / threshold / description
      Removed value: -"Minimum fuzzy score, default 0.85."
    • removedInput schema / required
      Removed value: -[
      -  "names"
      -]
  5. Changed3 schema fields changed
    • addedInput schema / properties / names / description
      Added value: +"Pipe-separated names, max 50."
    • addedInput schema / properties / threshold
      Added value: +{
      +  "description": "Minimum fuzzy score, default 0.85.",
      +  "type": "number"
      +}
    • addedInput schema / required
      Added value: +[
      +  "names"
      +]
  6. Changed3 schema fields changed
    • removedInput schema / properties / names / description
      Removed value: -"Names separated by | or , (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: -[
      -  "names"
      -]
  7. Changed5 schema fields changed
    • removedInput schema / properties / address
      Removed value: -{
      -  "description": "Crypto wallet address to screen.",
      -  "type": "string"
      -}
    • removedInput schema / properties / name
      Removed value: -{
      -  "description": "Counterparty or company name to screen against OFAC, UK OFSI and EU lists.",
      -  "type": "string"
      -}
    • addedInput schema / properties / names
      Added value: +{
      +  "description": "Names separated by | or , (alias: q).",
      +  "type": "string"
      +}
    • 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: +[
      +  "names"
      +]
  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.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. It usefully states the price, payment asset and chain, x402 payment location, and HTTP endpoint, which are important behavioral details. It still omits return format, screening criteria, error behavior, and what threshold controls, leaving meaningful gaps for a paid screening call.

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 description is short and front-loads the core action and batch limit before payment and endpoint details. Every sentence carries operational information, though the raw HTTP endpoint is less essential for an MCP caller and slightly clutters the otherwise focused description.

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?

The tool has two parameters, zero schema description coverage, no annotations, and no output schema, so the description must do more work. It covers payment and the names format but omits threshold semantics, expected screening output, and behavior when the 25-name limit is exceeded. This is not complete enough for a paid sanctions-screening batch tool.

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%, so the description must compensate. It explains that names are pipe-separated and capped at 25, which is valuable, but it never mentions the threshold parameter or what values mean. One of the two parameters is therefore left with no semantics beyond its bare schema type.

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?

The description states a specific verb and resource: screen names for sanctions in a batch call. It adds a useful scope constraint, up to 25 pipe-separated names, which distinguishes it from single-name screening siblings. It does not explicitly name the single-record alternative, but the batch purpose is clear.

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 phrase 'up to 25 pipe-separated names in one call' implies when to use this tool: when screening multiple names at once. However, it does not explicitly say when to choose a sibling such as check_sanctions__screen or check_sanctions__address, nor does it state what to do for a single name or over 25 names.

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