Skip to main content
Glama
FTHTrading

Genesis402

by FTHTrading
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Public-data sanctions-list signal for one address on any cha

genesis402_screen_sanctions

Screen a crypto address against OFAC SDN and community blocklists. Get sources and evidence hash to flag sanctions risk in one call.

Instructions

Paid (price from the live 402 quote). Public-data sanctions-list signal for one address on any chain: OFAC SDN digital-currency entries plus community blocklists. Use as a fast first gate on a counterparty address. The result lists its sources and an evidence hash. Automated heuristic signal from public data: not KYC, not a compliance determination, not legal advice. For a fuller risk picture use genesis402_wallet_brief.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe crypto address to screen, as a string (4 to 120 characters).
payment_signatureNoOptional. 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.2
    • addedInput schema / properties / address / description
      Added value: +"The crypto address to screen, as a string (4 to 120 characters)."
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first."New value: +"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."
  2. First observedv0.3.1

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses that the tool is paid, requires a live 402 quote, is an automated heuristic signal, and is not KYC/compliance/legal advice. It also explains what the result contains (sources and evidence hash). This adds meaningful behavioral context beyond the sparse annotations.

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?

The description is compact and front-loaded with the most important facts: paid, public-data signal, one address. Each sentence adds distinct value, and there is no redundant or filler content.

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?

For a two-parameter tool with no output schema, the description covers cost, input scope, data sources, output contents, limitations, and the sibling alternative. An agent has everything needed to decide when to call it and what to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already fully documents both parameters. The description adds the payment context but does not materially improve parameter understanding beyond what the schema provides, so the baseline score of 3 is appropriate.

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 names a specific action ('screen'), a specific resource ('one address on any chain'), and the exact data sources (OFAC SDN digital-currency entries plus community blocklists). It also distinguishes itself from the sibling wallet_brief by framing itself as a 'fast first gate.'

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?

It explicitly tells the agent when to use the tool ('Use as a fast first gate on a counterparty address') and directs to the alternative for deeper analysis ('For a fuller risk picture use genesis402_wallet_brief'). This is clear routing guidance with no ambiguity.

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

Deploy Server

Other Tools