Skip to main content
Glama

OFAC Name Screen Payment Quote

sanctions_screen_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/sanctions/screen (base $0.01; USDC on Base only); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?name=Example Name (optional country, dob, type=individual|entity|vessel|aircraft). No match is not a clearance.. Screen one name against the OFAC SDN list and the OFAC Consolidated list. Optional country, date of birth and type. Matches include a score, list name, entry id, programs and the list publish date. No match is not a clearance. Bad input or a list that did not load: not charged. USDC on Base only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral facts on top: the exact price and currency/chain constraint (USDC on Base only), the billing rule that bad input or an unloaded list is not charged, and the safety caveat that no match is not a clearance. These are billing and correctness semantics an agent cannot get from the annotations.

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

Conciseness3/5

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

The price and the 'never runs the check or pays' disclaimer are front-loaded, which is correct. However, 'No match is not a clearance' and 'USDC on Base only' each appear twice, and there is a stray double period ('clearance..'), so the text is visibly redundant rather than tight.

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 no input parameters and no output schema, the description carries the full load and does: it gives the endpoint, price, payment protocol, query shape, the fields a match returns (score, list name, entry id, programs, publish date), and the charging exceptions. Nothing an agent needs to call it correctly or interpret the quote 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 (schema coverage 100%), so the baseline is 4. The description goes further by documenting the underlying GET query surface — name plus optional country, dob, and an enumerated type of individual|entity|vessel|aircraft — which is useful context even though those are HTTP arguments rather than tool inputs.

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 uses a specific verb and resource combination: it returns payment terms for a named OFAC screening endpoint, and explicitly states the negative scope ('this tool never runs the check or pays'). That single clause separates it from an actual screening operation and from every sibling *_quote tool an agent might otherwise confuse it with.

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?

It states the follow-on action clearly: pay the 402 over HTTP with x402 v2, so an agent knows this call is a price-discovery step rather than the check itself. It does not name a specific alternative tool or spell out when-not to call it (e.g., if price is already known), which keeps it below a 5.

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.