Skip to main content
Glama

check_sanctions__changes

Sanctions changelog: additions and removals since a date, plus official OFAC recent actions. 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/changes

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

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / days
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "type": "number"
      +}
    • removedInput schema / properties / since
      Removed value: -{
      -  "type": "string"
      -}
  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 / since
      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. Changed6 schema fields changed
    • addedInput schema / properties / address
      Added value: +{
      +  "description": "Crypto wallet address to screen",
      +  "type": "string"
      +}
    • removedInput schema / properties / days
      Removed value: -{
      -  "type": "number"
      -}
    • 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
      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"
      +}
  4. Changed3 schema fields changed
    • removedInput schema / properties / days / description
      Removed value: -"Look-back window in days, default 7."
    • removedInput schema / properties / limit / description
      Removed value: -"Maximum entries, default 20."
    • changedInput schema / properties / limit / type
      Previous value: -"integer"New value: +"number"
  5. Changed2 schema fields changed
    • addedInput schema / properties / days / description
      Added value: +"Look-back window in days, default 7."
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Maximum entries, default 20.",
      +  "type": "integer"
      +}
  6. Changed2 schema fields changed
    • removedInput schema / properties / days / description
      Removed value: -"Look-back window in days, default 30."
    • removedInput schema / properties / limit
      Removed value: -{
      -  "description": "Max changes returned, default 20.",
      -  "type": "integer"
      -}
  7. Changed5 schema fields changed
    • removedInput schema / properties / address
      Removed value: -{
      -  "description": "Crypto wallet address to screen.",
      -  "type": "string"
      -}
    • addedInput schema / properties / days
      Added value: +{
      +  "description": "Look-back window in days, default 30.",
      +  "type": "number"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Max changes returned, default 20.",
      +  "type": "integer"
      +}
    • 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"
      -}
  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.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does disclose the two most consequential behaviors: a $0.01 per-call cost and that payment must be supplied via params._meta["x402/payment"], which is not in the input schema at all. It does not describe rate limits, response shape, or whether 'days' vs 'limit' constrain the changelog depth, leaving some 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?

Purpose is front-loaded in a single clause, then operational facts (price, payment vehicle, HTTP endpoint) follow compactly with no filler. Slightly dense but every sentence carries information an agent would otherwise have to guess.

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?

Given no annotations, no output schema, and zero schema coverage on both parameters, the description covers purpose, cost, and payment mechanics well but leaves the return shape and the meaning/defaults of 'days' and 'limit' unexplained. An agent could call it, but not confidently tune the parameters.

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 explain the two parameters and does not: neither 'days' nor 'limit' is defined, and 'since a date' arguably conflicts with a numeric 'days' parameter. The only parameter-adjacent value is the disclosure of the non-schema _meta payment field.

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 names a specific verb-plus-resource: a sanctions changelog of additions and removals since a date, plus OFAC recent actions. That is concrete enough for an agent to distinguish it from point-in-time siblings like check_sanctions__address or check_sanctions__screen, though it never names an alternative explicitly.

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 only implied: an agent can infer this is for 'what changed lately' questions rather than for screening a specific entity. There is no explicit when-to-use or when-not-to-use guidance, and no guidance about how far back to look relative to the sibling screening 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