Skip to main content
Glama

EU e-invoicing and business checks (EN 16931, Peppol, VAT, sanctions)

Screen a name against EU/UN/OFAC/UK sanctions

screen_sanctions
Read-onlyIdempotent

Screen a person or company name against official EU, UN, OFAC SDN and UK sanctions lists. Fuzzy matching with transliteration; returns candidate matches with 0-100 scores, list, programme, DOB. A potential match needs human review; this is a screening aid, not legal advice.

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

Input Schema

NameRequiredDescriptionDefault
nameYesPerson or company name to screen.
countryNoOptional ISO two-letter country code, to narrow matches.
thresholdNoMinimum fuzzy match score from 0 to 100 (default 85); lower finds more possible matches.
birth_yearNoOptional birth year of a person, to narrow matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / birth_year / description
      Added value: +"Optional birth year of a person, to narrow matches."
    • addedInput schema / properties / country / description
      Added value: +"Optional ISO two-letter country code, to narrow matches."
    • addedInput schema / properties / name / description
      Added value: +"Person or company name to screen."
    • addedInput schema / properties / threshold / description
      Added value: +"Minimum fuzzy match score from 0 to 100 (default 85); lower finds more possible matches."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: fuzzy matching with transliteration, scored 0-100 candidates, and the explicit caveat that a hit is a review signal rather than a determination. It does not say how many candidates are returned or what an empty result means, which keeps it below 5.

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?

Three short sentences, front-loaded with the verb and list sources, then behavior, then the human-review caveat. Nothing is repeated from the title verbatim and every sentence carries information an agent would use.

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?

There is no output schema, and the description compensates by naming the return fields (candidate matches, 0-100 score, list, programme, DOB) and the human-review requirement. What is missing is result-count/pagination behavior and the meaning of a no-match outcome for a compliance-sensitive tool.

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

Parameters3/5

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

Schema description coverage is 100%, so name, country, threshold and birth_year are all documented in the schema itself. The description reinforces the scoring scale (0-100) and fuzzy/transliteration behavior, but adds no syntax or format detail for the narrowing parameters beyond what the schema already says; baseline 3 applies.

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 (screen) plus resource (person or company name) and enumerates the exact list sources (EU, UN, OFAC SDN, UK), which distinguishes it from registry/company-lookup siblings. An agent can tell immediately what this does without opening the schema.

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 description frames the tool as a screening aid and warns that potential matches require human review and are not legal advice, which is useful framing for interpreting results. However, it gives no guidance on when to choose this over siblings like kyb_check, due_diligence_report, or verify_batch, and no preconditions or exclusions are stated.

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.