Skip to main content
Glama

Sanctions Screen (OFAC, UN, EU, UK)

Batch sanctions screening

screen_sanctions_batch
Read-only

Screen up to 10 names in one call against OFAC, UN, EU and UK sanctions lists. $0.05 per call after the free daily quota.

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": {
      "names": "<names>"
    },
    "name": "screen_sanctions_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
listsNo
namesYes
min_scoreNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety behavior is partly covered. The description usefully adds the list providers, the 10-name cap, and the $0.05 per-call cost after the free daily quota, but it does not explain result semantics such as scores, matches, or partial failures.

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 tightly written sentences with no wasted wording. The batch size and screening providers are front-loaded, and cost is placed second.

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?

For a read-only sanctions screening tool with no output schema, the definition covers the core operation, provider lists, batch limit, and pricing. However, with 0% schema description coverage it leaves key inputs such as 'type' and 'min_score' unexplained, which is a meaningful gap for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description must carry the burden of explaining them. It mentions the sanctions lists and the batch size, but adds no meaning for 'type', 'min_score', or the fact that 'lists' is optional and filters which providers are queried.

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

Purpose4/5

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

The description states a specific verb and resource ('Screen ... names ... against ... sanctions lists') and clarifies the batch scope with 'up to 10 names in one call.' This distinguishes it reasonably from the single-name sibling screen_sanctions, though it does not name that alternative explicitly.

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 batch limit and per-call pricing imply that this tool is intended for screening multiple names at once, but the description never explicitly says when to choose it over screen_sanctions or when a single-name call is preferable. It also gives no guidance on quota exhaustion beyond noting that pricing applies after the free daily quota.

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