Skip to main content
Glama

Check country sanctions

screen_country
Read-only

Check whether a country or region carries sanctions designations (OFAC's programs). lists: optional comma-separated list slugs; add fatf (e.g. "ofac,fatf") to also check FATF's black and grey lists, which set flagged but never sanctioned.

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": {
      "country": "<country>"
    },
    "name": "screen_country"
  }
}

Input Schema

NameRequiredDescriptionDefault
listsNo
countryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral detail: the external dependency on OFAC programs and the asymmetric result semantics where FATF membership sets `flagged` but never `sanctioned`, which tells the agent how to interpret output the annotations cannot convey.

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?

Two sentences, front-loaded with the core purpose and then the optional-parameter rule with an inline example. Every clause adds information: no filler, no restatement of the title, no redundant re-explanation of annotations.

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?

An output schema exists, so return values need not be described, and the definition even clarifies two result fields. The weaker area is input completeness for a screening tool — acceptable values for `lists` beyond `fatf` (is `ofac` a valid slug? are others?) and the expected `country` format are left unresolved, which matters for correct invocation of a 2-parameter tool with 0% schema coverage.

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 description coverage is 0%, so the description must carry the parameter burden, and it does so well for `lists`: comma-separated slugs, the `fatf` token, a concrete example ('ofac,fatf'), and the resulting semantics (sets `flagged` but never `sanctioned`). The `country` parameter gets no format guidance (name vs ISO code) and no enumeration of valid slugs besides `fatf`, so one gap remains.

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?

The description gives a concrete verb ('check') and a precise resource ('whether a country or region carries sanctions designations'), and names the specific data source (OFAC programs). The entity scope (country/region) is stated explicitly enough that an agent can separate this from screen_name, screen_vessel, or screen_crypto_address without inspecting 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?

Conditional guidance exists for the optional `lists` parameter — add `fatf` to also check FATF black and grey lists — but there is no statement of when to reach for this tool instead of the other screening tools, nor any prerequisite or exclusion guidance. Usage is largely inferable from the entity type rather than instructed.

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