Skip to main content
Glama

Sanctions Screening (OFAC/EU/UN)

50 Percent Rule ownership screening

screen_ownership_50pct

Paid: $0.05 per call, paid via x402 in USDC on Base. STATUS: planned, not yet available. Checks whether an entity is blocked by operation of the OFAC 50 Percent Rule (owned 50% or more, in the aggregate, by designated persons) even when it does not itself appear on any list. Requires beneficial-ownership graph analysis, not list lookup.

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": {
      "query_name": "<query_name>"
    },
    "name": "screen_ownership_50pct"
  }
}

Input Schema

NameRequiredDescriptionDefault
query_nameYes
jurisdictionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the $0.05 per-call cost, the x402/USDC-on-Base payment mechanism, and the critical fact that the tool is planned and not yet available. It stops short of saying what the response contains or what happens when ownership cannot be established.

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?

Four short sentences with no filler; every clause carries information. The ordering is slightly off for an agent deciding whether to call: commercial and status metadata lead, while the actual purpose arrives third, so the reader must pass two housekeeping sentences before learning what the tool does.

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?

Pricing, availability status, and the analytical basis are covered, which is more than most definitions offer, but with no annotations, no output schema, and zero parameter documentation, the definition is not complete enough to specify inputs or expected results. Reasonable for a planned endpoint, thin for an invocable tool.

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% for both parameters, so the description must compensate and does not — neither query_name nor jurisdiction is mentioned. In particular, the meaning and effect of jurisdiction, and whether the ownership stake is queried by name only, are left entirely undocumented.

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 precise verb and resource: it checks whether an entity is blocked by operation of the OFAC 50 Percent Rule via aggregate ownership, and explicitly contrasts that with list lookup. An agent can distinguish this from screen_name or screen_batch without opening any schema.

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

Usage Guidelines3/5

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

The clause 'Requires beneficial-ownership graph analysis, not list lookup' implies when this tool is the right choice versus a plain list screen, but no sibling is named and no explicit precondition or exclusion is given. Usage is inferable rather than stated.

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.