Skip to main content
Glama

get_ofac_sanctions_screening

Read-only

Use when onboarding a vendor, counterparty, or individual requires OFAC sanctions screening with attested results. Screens Treasury SDN and Consolidated lists with conservative fuzzy matching, match methodology metadata, and list version binding for GSR verification. Source: Treasury OFAC synced lists. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $1.00 USDC per call.

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": {
      "entity_name": "<entity_name>"
    },
    "name": "get_ofac_sanctions_screening"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasNo
countryNo
entity_nameYes
entity_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses matching method ('conservative fuzzy matching'), that methodology metadata and list-version binding are included, that results are cryptographically attested with an out-of-band verification URL, and the exact cost ($1.00 USDC per call). Cost and verification path are operationally decisive details an agent could not get from annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the usage trigger, then mechanics, then attestation and pricing — a sensible ordering with little waste. 'Post-quantum signed settlement receipt' leans promotional but still signals the attestation strength.

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?

There is no output schema, so the description should carry the burden of describing the result, yet it only hints at 'match methodology metadata' and 'list version binding' without saying what a response contains (match flag, score, matched list entry). Combined with zero parameter documentation, an agent can invoke it but cannot predict or interpret the result well.

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, and the description never mentions entity_name, alias, country, or entity_type. It gives no guidance on how country narrows a match or how entity_type (the sole enum) changes screening behavior, so an agent must guess at parameter impact.

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 verb and resource: 'Screens Treasury SDN and Consolidated lists,' and opens with the onboarding/vendor/counterparty context. The OFAC/Treasury naming implicitly separates it from the OIG and SAM exclusion screening siblings, but no sibling is explicitly named or contrasted.

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?

The first sentence gives a clear triggering condition ('Use when onboarding a vendor, counterparty, or individual requires OFAC sanctions screening with attested results'), which is enough for an agent to recognize the context. It does not state when NOT to use it or point to the OIG/SAM alternatives when a different list is needed.

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