Skip to main content
Glama

Sanctions Screen (OFAC, UN, EU, UK)

Sanctions list freshness (free)

sanctions_lists_status
Read-only

Free. When the sanctions lists were last refreshed and how many entries each contains.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this as a safe read, so the description only needs to add context. It contributes two useful facts beyond the annotation, the lack of cost ('Free') and the shape of the payload (last-refresh times and entry counts), but says nothing about which lists are covered, caching, or auth expectations.

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?

A single sentence with no waste, front-loading the cost note and then the two pieces of information returned. Every clause earns its place for a zero-parameter status call.

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?

With no parameters, no output schema, and a read-only annotation, the definition is close to sufficient: it tells the agent what the call returns. It could be tighter by naming the covered list families, but nothing essential to invoking it is missing.

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?

The tool takes zero parameters, so there is no argument semantics to explain and the baseline of 4 applies. Nothing in the description misdescribes or invents parameter behavior.

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?

States a specific resource and scope: sanctions list refresh timestamps plus per-list entry counts. This is clearly a metadata/status tool rather than a screening tool, so an agent can distinguish it from screen_sanctions and screen_sanctions_batch without opening the schema, though the description never explicitly names those siblings.

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 leading 'Free.' is a cost signal that implies it is cheap to call, and the content implies a pre-screening freshness check. However, there is no explicit when-to-use or when-not guidance and no reference to the screening tools it complements.

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