Skip to main content
Glama

AurelianFlo

by com.aurelianflo

OFAC Wallet Screen

wallet_ofac_screen
Read-only

Screen one crypto wallet address against OFAC SDN digital currency designations and return exact hits, sanctioned entity metadata, asset coverage, and a manual-review signal. Use this for one-off status checks; use wallet_ofac_report for PDF/DOCX output or wallet_ofac_batch for multiple addresses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetNoOptional asset or network ticker filter such as ETH, USDC, XBT, TRX, ARB, or BSC.
addressYesCrypto wallet address to screen against OFAC SDN digital currency address designations.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoPrimary structured result payload for the tool.
errorNoMachine-readable error code or message when the tool fails.
outputNoNested renderer output when a workflow bundles an artifact render.
reportNoReport-shaped payload when available; null for status-only retrieval responses.
sourceNoSource label, route, dataset, or execution metadata for the result.
messageNoHuman-readable error or status message.
successNoWhether the tool completed successfully.
artifactNoInline generated file artifact. The service does not persist a hosted download URL.
artifactsNoArtifact rendering hints keyed by format.
artifact_summaryNoDelivery and rendering metadata for an inline generated artifact.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds value by detailing the return types (exact hits, metadata, coverage, manual-review signal) beyond the annotation, but does not cover other behavioral traits like rate limits or authentication requirements.

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?

Two sentences, front-loaded with the core action, no redundant information. Every sentence serves a purpose.

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?

Given the presence of an output schema and the simplicity of the tool, the description covers purpose, usage, and return types adequately. However, it omits any discussion of prerequisites or potential errors.

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 coverage is 100% with descriptions for both parameters. The description does not add significant meaning beyond the schema; it mentions the address and asset filter implicitly but does not elaborate on parameter semantics further.

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 clearly states the tool screens one crypto wallet address against OFAC SDN digital currency designations and returns specific results. It distinguishes from siblings by naming wallet_ofac_report and wallet_ofac_batch for different use cases.

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?

Explicitly states 'Use this for one-off status checks' and points to alternatives for PDF/DOCX output or multiple addresses, providing clear when-to-use and when-not-to-use guidance.

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

All AurelianFlo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Tools are generally distinct, with clear differentiators like single vs batch vs report output. The queue_saved_list and report_saved_retrieve could be confused but descriptions clarify their separate domains.

Naming Consistency4/5

Prefixes like compliance_, wallet_ofac_, report_, queue_ provide consistency within subdomains, though verb order varies (e.g., report_docx_generate vs queue_saved_list).

Tool Count4/5

11 tools are appropriate for a compliance server covering screening, reporting, and optimization. Slightly on the higher side but each tool serves a unique purpose.

Completeness4/5

Covers core workflows: screening, batch, reporting, EDD memos, exposure forecasting, queue optimization, and status checks. Minor gaps like no wallet set management, but overall comprehensive.

Resources