Skip to main content
Glama

Review a sanctions entry

get_sanctions_entry
Read-onlyIdempotent

Use this when the user wants an ofac check, ofac sdn list detail, or sanctions list check for a known positive uid. Reads both lists unless one is specified and returns aliases, programs, countries, truncated remarks and source dates. Do not use for identity confirmation, other government lists or ownership analysis.

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": {
      "uid": "<uid>"
    },
    "name": "get_sanctions_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYesPositive whole-number entry uid from a potential match. Example: 22790.
listNoOptional SDN or NON-SDN; omit to inspect both lists. Example: SDN.

Output Schema

NameRequiredDescriptionDefault
listsYes
notesYes
entriesYes
warningsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive open-world lookup. The description adds useful behavior beyond that: it reads both lists unless one is specified, returns aliases/programs/countries/remarks/dates, and notes that remarks are truncated.

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?

The description is three tight sentences, front-loads the intended use case, then states return contents and exclusions. Every sentence contributes either routing guidance or behavioral context.

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?

With annotations covering safety and an output schema covering return shape, the description supplies the remaining operational context: when to use it, when not to use it, default dual-list reading, and the nature of returned entry details. Nothing essential for correct invocation 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?

Schema coverage is 100%, so the baseline is 3 because the schema already documents both parameters. The description still adds meaningful semantics by emphasizing that the uid must be a known positive match and that the list parameter controls whether one list or both lists are read.

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 states a specific retrieval action for a sanctions entry identified by a known positive uid, and explicitly names the content returned: aliases, programs, countries, remarks, and source dates. It also distinguishes the tool from identity confirmation, other government lists, and ownership analysis, so an agent can tell what it is for 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 Guidelines5/5

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

It gives explicit use conditions ('when the user wants an ofac check... for a known positive uid') and explicit exclusions ('Do not use for identity confirmation, other government lists or ownership analysis'). The boundary against the sibling screen_names tool is implied clearly through 'known positive uid' versus name screening.

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