Skip to main content
Glama

check_sanctions__watchlist

Re-screen a fixed counterparty list; report only what changed since N days ago. 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/watchlist

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

Input Schema

NameRequiredDescriptionDefault
daysNo
namesNo
thresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / days
      Added value: +{
      +  "type": "number"
      +}
    • 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. Changed5 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
      Added value: +{
      +  "description": "Match similarity threshold, default 0.85",
      +  "maximum": 1,
      +  "minimum": 0.5,
      +  "type": "number"
      +}
  4. Changed4 schema fields changed
    • removedInput schema / properties / days
      Removed value: -{
      -  "description": "Look-back window in days, default 7.",
      -  "type": "number"
      -}
    • removedInput schema / properties / names / description
      Removed value: -"Pipe-separated names, max 50."
    • removedInput schema / properties / threshold
      Removed value: -{
      -  "description": "Minimum fuzzy score, default 0.85.",
      -  "type": "number"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "names"
      -]
  5. Changed4 schema fields changed
    • addedInput schema / properties / days
      Added value: +{
      +  "description": "Look-back window in days, default 7.",
      +  "type": "number"
      +}
    • 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. Changed2 schema fields changed
    • removedInput schema / properties / names / description
      Removed value: -"Your counterparties separated by | or , ."
    • 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": "Your counterparties separated by | or , .",
      +  "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: +[
      +  "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.2/5.0
Behavior3/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 add real value: cost ($0.01/call), payment rail (USDC on Base, x402 via params._meta), and transport (HTTP GET endpoint). It does not disclose what 'changed' means in the response, whether re-screening is idempotent, what happens on payment failure, or any 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The behavioral scope is front-loaded in the first clause, with commercial and transport details following. Information density is high with no filler, though the endpoint/payment sentence is dense and mixes pricing, payment encoding, and HTTP method into one line.

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 3-parameter, no-annotation, no-output-schema tool, the description covers purpose, cost, payment, and endpoint but leaves the entire parameter surface and the semantics of the returned 'changes' undefined. An agent can form a request but cannot confidently choose values for names or threshold.

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 all three parameters, so the description must compensate and largely does not: only 'days' is obliquely implied by 'since N days ago' (no default, no units bound). 'names' and 'threshold' are never mentioned, and 'names' actively conflicts with the claim of a 'fixed counterparty list'.

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 ('re-screen') and resource ('fixed counterparty list') plus a delta scope ('report only what changed since N days ago'), which separates it from full screening tools. The notion of a 'fixed' list is left unexplained, and it is unclear how that list relates to the 'names' parameter, so it falls short of full sibling-level differentiation.

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 delta framing implies a use case (periodic re-screening rather than fresh screening), but there is no explicit when-to-use/when-not guidance and no named alternative among the many screening siblings. An agent must infer that this is for recurring monitoring rather than one-off checks.

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