Skip to main content
Glama

Sanctions Screening (OFAC/EU/UN)

Sanctions lists metadata

sanctions_lists_metadata

Free. Returns which sanctions lists are loaded, the data version, and the record count. Use this to decide whether the data is fresh enough for your purpose before screening.

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_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose the important traits: it is a read-only lookup, it is "Free" (no quota/cost concern), and it has no side effects implied by the zero-parameter return-only wording. It does not mention authentication needs or rate limits, so a small gap remains.

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, led by the highest-value qualifier ("Free") and then the return contents, ending with the routing hint. No sentence is redundant and nothing is buried.

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

Completeness5/5

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

There is no output schema, but the description effectively documents the return payload (lists loaded, data version, record count), so an agent knows what it will get. For a zero-parameter read-only tool this covers everything needed to call it correctly.

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 the baseline is 4; there is no argument meaning the description needs to compensate for. The description correctly signals that no inputs are required by describing only what is returned.

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?

"Returns which sanctions lists are loaded, the data version, and the record count" gives a specific verb (returns) and enumerates exactly what metadata is produced. Combined with the final clause ("before screening"), an agent can tell this apart from the sibling screening tools without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use this to decide whether the data is fresh enough for your purpose before screening" states the decision this tool supports and positions it ahead of the screen_* siblings. It stops short of naming an explicit alternative or a when-not-to-use condition, so it is clear context rather than a full routing rule.

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.