Skip to main content
Glama

List sanctions listing changes

sanctions_list_changes
Read-onlyIdempotent

Returns additions, amendments and removals between official sanctions list snapshots: US Treasury OFAC SDN and Consolidated, UK HM Treasury/FCDO, EU Financial Sanctions Files and Canada (Canada coverage is entity-only; Australia pending, not loaded yet). Use it to monitor what changed since a date; use sanctions_search_entries when you have a name, and sanctions_get_entry when you already know a list and id. Inputs (all optional, they narrow together): since (YYYY-MM-DD, default 7 days ago), list, change (added/amended/removed), limit (1 to 50, default 20) and cursor (next_cursor from the previous page, same filters). Output: changes[] with entry, changed fields, observed_at and proof (publisher page, SHA-256, source date), plus lists[] check times and next_cursor for paging or polling; lists are checked about twice a day. This is a monitoring feed, not a clearance decision: no change means none observed, the UN list is not covered, and the official publications are authoritative. Changes across 5 official lists since 2026-10-22; earlier changes are not available. Terms: read-only; MCP calls are never charged. Without a key, metered routes give 10 successful answers a day free, as short samples (up to 3 records, without file proof, history or paging cursor) where a paid HTTP address exists (unmetered routes are unlimited); errors do not count. On the paid HTTP routes, errors are free, and so are empty answers except a sanctions name search with no match when every loaded list it checks is fresh (lists not loaded yet are named in the answer). An optional API key keeps its prepaid-credit policy. When the free answers run out, the error names the HTTP alternative.

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": "sanctions_list_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNoOne list only Allowed: ofac-sdn, ofac-consolidated, uk, eu, ca, au; e.g. ofac-sdn.
limitNoChanges per page, 1 to 50 (default 20); e.g. 20.
sinceNoChanges observed on or after this date, YYYY-MM-DD (default: 7 days ago); e.g. 2026-10-01. Must be a parseable YYYY-MM-DD date.
changeNoOne kind of change only Allowed: added, amended, removed; e.g. added.
cursorNoOpaque next_cursor from this tool's prior answer; s followed by 1 to 12 digits, e.g. s0. Keep filters unchanged; omit on first call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / list / description
      Previous value: -"One list only Allowed: ofac-sdn, ofac-consolidated, uk, eu; e.g. ofac-sdn."New value: +"One list only Allowed: ofac-sdn, ofac-consolidated, uk, eu, ca, au; e.g. ofac-sdn."
    • changedInput schema / properties / list / enum
      Previous value: -[
      -  "ofac-sdn",
      -  "ofac-consolidated",
      -  "uk",
      -  "eu"
      -]New value: +[
      +  "ofac-sdn",
      +  "ofac-consolidated",
      +  "uk",
      +  "eu",
      +  "ca",
      +  "au"
      +]
  2. Changed11 schema fields changed
    • changedInput schema / properties / change / description
      Previous value: -"One kind of change only"New value: +"One kind of change only Allowed: added, amended, removed; e.g. added."
    • addedInput schema / properties / change / examples
      Added value: +[
      +  "added"
      +]
    • changedInput schema / properties / cursor / description
      Previous value: -"next_cursor from a previous answer"New value: +"Opaque next_cursor from this tool's prior answer; s followed by 1 to 12 digits, e.g. s0. Keep filters unchanged; omit on first call."
    • addedInput schema / properties / cursor / examples
      Added value: +[
      +  "s0"
      +]
    • addedInput schema / properties / cursor / pattern
      Added value: +"^s[0-9]{1,12}$"
    • changedInput schema / properties / limit / description
      Previous value: -"Changes per page, 1 to 50 (default 20)"New value: +"Changes per page, 1 to 50 (default 20); e.g. 20."
    • addedInput schema / properties / limit / examples
      Added value: +[
      +  20
      +]
    • changedInput schema / properties / list / description
      Previous value: -"One list only"New value: +"One list only Allowed: ofac-sdn, ofac-consolidated, uk, eu; e.g. ofac-sdn."
    • addedInput schema / properties / list / examples
      Added value: +[
      +  "ofac-sdn"
      +]
    • changedInput schema / properties / since / description
      Previous value: -"Changes observed on or after this date, YYYY-MM-DD (default: 7 days ago)"New value: +"Changes observed on or after this date, YYYY-MM-DD (default: 7 days ago); e.g. 2026-10-01. Must be a parseable YYYY-MM-DD date."
    • addedInput schema / properties / since / examples
      Added value: +[
      +  "2026-10-01"
      +]
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

The description goes well beyond the readOnly/openWorld/idempotent annotations: it discloses coverage gaps (Canada entity-only, Australia pending/not loaded), the history horizon (changes since 2026-10-22 only), the refresh cadence (lists checked about twice a day), the no-change semantics, and the metering/rate-limit behaviour including free-tier sample truncation. The pricing-and-quota paragraph is dense and partly tangential to invocation, which keeps this just short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Purpose, alternatives and outputs are front-loaded well, but the back half is a long, run-on block of billing rules (free answers, samples, paid HTTP routes, prepaid credit, error handling) that would be better placed in one short sentence or a docs pointer. Several clauses are repeated in spirit ('errors do not count' vs 'on the paid HTTP routes, errors are free'), costing scanability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so: changes[] with entry, changed fields, observed_at and proof (publisher page, SHA-256, source date), plus lists[] check times and next_cursor for paging or polling. Together with the coverage caveats and auth/metering notes, nothing an agent needs to call or interpret this tool is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics the schema does not: all inputs are optional and 'narrow together' (conjunctive filtering), and cursor must carry the same filters as the prior page. It also restates the since default and limit range, which is redundant but harmless.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource — returns additions, amendments and removals between official sanctions list snapshots — and names the exact publishers covered (OFAC SDN/Consolidated, UK, EU, Canada). It explicitly distinguishes itself from sanctions_search_entries (name lookup) and sanctions_get_entry (known list+id), so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

States the use case directly (monitor what changed since a date) and names both alternatives with the condition that selects each: search when you have a name, get_entry when you know list and id. It also frames scope exclusions (monitoring feed, not a clearance decision; UN list not covered), which is exactly the when/when-not guidance an agent needs.

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.