Skip to main content
Glama

Search the Swiss sanctions list

search_sanctions_list
Read-only

Screen a person, company, or vessel name against Switzerland's consolidated sanctions list to identify potential matches; filter by type or programme and include delisted entries.

Instructions

Screen a person, company or vessel name against the Swiss consolidated sanctions list (SECO, all embargo programmes: Russia/Ukraine, Belarus, Iran, Syria, North Korea, ISIL/Al-Qaida, …). Matching is case- and diacritic-insensitive over primary names, aliases and Latin transliterations; all query words must match (as words or word prefixes). Returns current listings only unless include_delisted=true. A hit is a lead, not a legal determination: compare birth dates, nationality and documents via get_sanctions_entry. Example: {name: 'Rotenberg'}, {name: 'Aeroflot', type: 'entity'}.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName or name fragment, e.g. 'Arkady Rotenberg', 'Sovcomflot'
typeNoRestrict to individuals, entities (companies/organisations) or objects (vessels, aircraft)
limitNo
programNoRestrict to a sanctions programme, e.g. 'Ukraine', 'Iran', 'Syria' (see list_sanctions_programs)
include_delistedNoAlso return entries that have since been de-listed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the readOnly/openWorld annotations by disclosing matching behavior: case- and diacritic-insensitive matching across primary names, aliases and Latin transliterations, and that all query words must match as words or prefixes. The caveat that a hit is not a legal determination is valuable behavioral context, though result shape and pagination are not described.

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-loads the core action, scope and matching rules in a compact sequence, followed by the delisted default and the follow-up caveat. The single long parenthetical listing programmes is dense but informative, and no sentence is merely filler.

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

Completeness4/5

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

No output schema exists, but the description covers the key behavioral facts an agent needs: matching rules, default exclusion of delisted entries, programme scope and the need to verify hits via get_sanctions_entry. It does not describe the result fields or limit/pagination behavior, which leaves a small gap.

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 high at 80%, so the baseline is 3, but the description adds meaningful semantics about how the name parameter is matched, including prefix/word behavior. It also clarifies that include_delisted controls whether historical listings are returned, adding value beyond the schema's own parameter descriptions.

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: screening a person, company or vessel name against the Swiss consolidated SECO sanctions list. It names the covered embargo programmes and clearly distinguishes itself from get_sanctions_entry by framing itself as the search step.

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?

Explicitly says a hit is a lead, not a legal determination, and routes follow-up comparison of birth dates, nationality and documents to get_sanctions_entry. It also states that delisted entries are excluded unless include_delisted=true, which is a concrete usage rule.

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