Skip to main content
Glama

Stratalize Intelligence

Get Ofac Sanctions Screening

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
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that – conservative fuzzy matching, match-methodology metadata, list-version binding for GSR verification, and a $1.00 USDC per-call cost. However, it does not disclose latency, sync cadence in concrete terms, or what a low-confidence match looks like, so it remains a moderate rather than rich disclosure.

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?

The definition front-loads the usage trigger first, which is the right ordering, and each sentence is short. The attestation and verification-URL sentences are somewhat promotional but do convey actionable trust information, so little is truly wasted.

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?

The tool has no output schema, and the definition compensates by naming the return components: match results, match-methodology metadata, and list-version binding. The main missing piece is parameter-level guidance, which is not covered anywhere else. Relative to a four-parameter screening tool, this is nearly complete.

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%, so the description carries the full burden of explaining four parameters, but it explains none of them. It never defines alias, country, or the entity_type enum values, and only indirectly hints at entity types through the screening-target phrasing. With zero-coverage parameters left undocumented, this is a significant gap.

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?

States a specific verb and resource: screens Treasury SDN and Consolidated OFAC lists, and names the entity classes (vendor, counterparty, individual) it applies to. Because it identifies the exact source lists, an agent can distinguish it from the sibling OFAC-adjacent screeners (OIG exclusion, SAM exclusion) 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 when onboarding a vendor, counterparty, or individual requires OFAC sanctions screening" gives a clear triggering condition. It does not state when to prefer this over the OIG or SAM screening siblings, nor any exclusions, so it stops short of full routing guidance.

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