Skip to main content
Glama
UK Business Tools - Ledgerhall

UK Business Tools - Ledgerhall

Screen a Name Against Sanctions Lists

dd_sanctions_screen
Read-onlyIdempotent

Screen a person or company name against UK OFSI, US OFAC, EU and UN sanctions lists to check whether a counterparty, officer or PSC is listed. Reports which lists loaded and any partial coverage.

Instructions

Screen a name against the UK (OFSI), US (OFAC), EU and UN consolidated sanctions lists.

Returns every list entry whose primary name or alias matches, with the regime, source reference and listing date where the source gives one. Use it to check whether a counterparty — or its officers / persons with significant control — appears on a sanctions list.

MATCHING is deterministic: normalised exact + alias match (case-, accent- and punctuation-insensitive). A company/entity legal name matches reliably; PERSON names with transliteration variants may not (e.g. 'Mohammed' vs 'Muhamad'). An empty result is therefore NOT a guarantee of clearance, and a hit on a common name may be a false positive to disambiguate. This is a screening aid, not a compliance determination.

lists_screened reports which of OFSI/OFAC/EU/UN were actually loaded; lists_unavailable names those that were not, and is_partial is true whenever it is non-empty or the lists are a previous load that could not be refreshed (as_at then shows when they were loaded). When is_partial is true an empty hits is UNRESOLVED, not clearance. If no list could be loaded at all the call raises a retryable error rather than returning an empty screen. as_at is when the lists were last refreshed on this server.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "dd_sanctions_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPerson or company/entity name to screen against the consolidated sanctions lists.
entity_typeNoOptional filter: 'person' or 'entity' (a company is an 'entity'). Any other value is rejected. Omit to screen both.

Output Schema

NameRequiredDescriptionDefault
hitsNoMatching list entries. An empty list means no exact/alias match on the screened lists — NOT a guarantee of clearance (see the tool description on matching limits).
as_atNoWhen this server last refreshed the loaded lists (ISO timestamp). Provenance for the screen — the lists update on designation.
queryYesThe name that was screened.
is_partialNoTrue when any expected list was unavailable, or when the lists are a previous load that could not be refreshed (see as_at). When true, an empty hits list must be treated as UNRESOLVED, not as clearance.
match_countYesNumber of list entries that matched the query.
lists_screenedNoWhich consolidated lists were fully loaded and actually screened for this call. A list absent here was NOT screened — see lists_unavailable. Note a list that failed part-way still contributes the entries it had already parsed, so a hit's list_source may name a list missing from here; that is a real match on a list this server does not consider fully screened, not a contradiction.
normalized_queryYesThe normalised form used for matching (upper-cased, accent- and punctuation-stripped, whitespace-collapsed).
lists_unavailableNoExpected lists that did not load, or loaded to zero records, and so were NOT screened. Non-empty means this screen is incomplete: a name on one of these lists would not appear in hits. Absence of evidence here is not evidence of absence.
entity_type_filterNoentity_type filter applied to the screen ('person'/'entity'), or null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.1
    • changedInput schema / properties / entity_type / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "person",
      +      "entity"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / entity_type / description
      Previous value: -"Optional filter: 'person' or 'entity'. Omit to screen both."New value: +"Optional filter: 'person' or 'entity' (a company is an 'entity'). Any other value is rejected. Omit to screen both."
  2. Changed4 schema fields changedv0.3.0
    • changedOutput schema / properties / hits / items / properties / reference / description
      Previous value: -"The source's own reference for the listing (OFSI Group ID, OFAC uid, EU reference number, or UN reference number)."New value: +"The source's own reference for the listing (FCDO Unique ID, OFAC uid, EU reference number, or UN reference number)."
    • addedOutput schema / properties / is_partial
      Added value: +{
      +  "default": false,
      +  "description": "True when any expected list was unavailable, or when the lists are a previous load that could not be refreshed (see as_at). When true, an empty hits list must be treated as UNRESOLVED, not as clearance.",
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / lists_screened / description
      Previous value: -"Which consolidated lists were loaded and actually screened for this call. A list absent here failed to load and was NOT screened — treat the result as partial if any of OFSI/OFAC/EU/UN is missing."New value: +"Which consolidated lists were fully loaded and actually screened for this call. A list absent here was NOT screened — see lists_unavailable. Note a list that failed part-way still contributes the entries it had already parsed, so a hit's list_source may name a list missing from here; that is a real match on a list this server does not consider fully screened, not a contradiction."
    • addedOutput schema / properties / lists_unavailable
      Added value: +{
      +  "description": "Expected lists that did not load, or loaded to zero records, and so were NOT screened. Non-empty means this screen is incomplete: a name on one of these lists would not appear in hits. Absence of evidence here is not evidence of absence.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  3. First observedv0.2.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, yet the description adds substantial behavior: deterministic normalised exact+alias matching, known failure modes for transliterated person names, false-positive risk on common names, partial-load semantics via lists_screened/lists_unavailable/is_partial, and a retryable error when no list loads. This is exactly the kind of context structured fields cannot carry.

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?

Front-loaded with the action and sources, then matching semantics, then result-interpretation rules, in a logical progression with zero filler. The uppercase emphasis on MATCHING and UNRESOLVED makes the two critical caveats scannable.

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?

For a screening tool whose worst failure mode is a false sense of clearance, the description covers reliability limits, partial-list states, error behavior and the meaning of as_at. Although an output schema exists, the interpretation guidance about empty hits being UNRESOLVED rather than clearance is essential and correctly included.

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 meaning by explaining that company/entity legal names match reliably while person names with transliteration variants may not — directly informing how to set entity_type and how to read results. It does not discuss length limits or the rejection behavior for invalid entity_type values, which the schema already covers.

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?

States a specific verb and resource (screen a name) and enumerates the exact data sources: UK OFSI, US OFAC, EU and UN consolidated lists. It also names the scope of subjects (counterparty, officers, PSCs), so an agent can tell immediately what the tool does and what it does not do, without a sibling sanctions tool being present.

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

Usage Guidelines4/5

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

Gives a clear when-to-use frame — checking whether a counterparty or its officers/PSCs appear on a sanctions list — plus an explicit caution that this is a screening aid, not a compliance determination. It stops short of naming an alternative tool or stating when not to call it, which keeps it below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools