Genesis402

Screen a name against UN, OFAC, EU, UK sanctions

genesis402_sanctions_name_screen

Screen a person or organisation name against UN, US OFAC SDN, EU and UK sanctions lists, including aliases and transliterations, and return match status with hit evidence.

Instructions

Paid ($0.02 USDC). Screen one person or organisation name against the UN, US OFAC SDN, EU and UK consolidated sanctions lists, including aliases and transliterations. Returns match, possible match or no match, each hit with list, list id, matched name and score, and the published date and SHA-256 of every list version used. For a company and its parents in one call use genesis402_counterparty_report; for a wallet address use genesis402_screen_sanctions. Screening signal only: not KYC, not a compliance determination, not legal advice. Payment: call once without payment_signature to get the exact price quote (nothing is charged or signed), then call again with the signed payment to receive the result and settlement details.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	The person or organisation name to screen, 3 to 200 characters.
`type`	No	Optional. Restricts matching to that kind of list entry.
`dob_year`	No	Optional four-digit birth year, used to flag hits with an inconsistent date of birth.
`payment_signature`	No	Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it.

Output Schema

TableJSON Schema

Name	Required	Description
`mode`	Yes	QUOTE_ONLY: price quote only, nothing signed or charged. PAID: the call was paid and result holds the data. FREE: the endpoint answered without payment.
`paid`	Yes	true only when a payment was settled for this call.
`price`	No	The Base USDC quote. Present on QUOTE_ONLY and on PAID calls made by a local payer; null when the rail offered no Base USDC lane or the caller signed the payment.
`result`	No	PAID or FREE: the endpoint's JSON result.
`resource`	No	QUOTE_ONLY: the full URL of the paid resource.
`how_to_pay`	No	QUOTE_ONLY: how to sign and resend the call.
`settlement`	No	PAID: decoded PAYMENT-RESPONSE settlement (transaction hash, network, payer), or null if the rail sent none.
`what_you_get`	No	QUOTE_ONLY: the rail's description of what the payment buys.
`payment_required_b64`	No	QUOTE_ONLY: the raw base64 PAYMENT-REQUIRED header, to sign with any x402 v2 client.
`also_accepted_networks`	No	QUOTE_ONLY: every network the 402 challenge accepts.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.3.6Oct 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only supply readOnlyHint=false and openWorldHint=true, which are too coarse to explain this tool. The description fills the gap richly: paid at $0.02 USDC, the first no-signature call is free and returns a price quote, the second call with a signed payment produces the result plus settlement details, and returns are tri-state (match/possible match/no match) accompanied by list versions and their SHA-256. That is exactly the kind of behavior an agent needs before invoking a paid, open-world tool.

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?

Front-loads cost and the core action, then the return shape, then sibling routing, then scope caveat, then the payment protocol. Dense but every sentence carries decision-relevant information; nothing is restated from the schema or annotations.

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?

An output schema exists, so return values need not be enumerated, yet the description still summarizes the match tiers and per-hit fields. Combined with the payment handshake and scope disclaimer, an agent has everything required to call this paid, open-world tool correctly on the first attempt.

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 would be 3, but the description adds genuine meaning: it notes matching includes aliases and transliterations, that results carry matched name and score per hit, and that dob_year is used to flag inconsistent birth years. It stops short of adding syntax guidance beyond the schema, hence 4 rather than 5.

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 (screen a name) and names the exact list set covered (UN, US OFAC SDN, EU, UK consolidated). It also explicitly distinguishes itself from the two nearest siblings, genesis402_counterparty_report and genesis402_screen_sanctions, so an agent can route 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 Guidelines5/5

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

Gives explicit when-to-use routing: 'For a company and its parents in one call use genesis402_counterparty_report; for a wallet address use genesis402_screen_sanctions.' It also states the scope boundary ('Screening signal only: not KYC, not a compliance determination, not legal advice') and the required two-call payment sequence.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.