Skip to main content
Glama

AML Screening Report

sv_aml_report
Read-only

Audit-grade sanctions screening report: the $0.05 verdict expanded into per-layer status + latency, full name-match detail (score, dataset, entity id), address-format detection, and a deterministic per-day reportId for audit dedup. Batch: addresses=<a,b,c> up to 5 at the same flat price. Fail-closed — verdict "unscreened" when the oracle cannot be reached. Informational only — not compliance advice. Free with X-ORKID-API-Key or $0.25 USDC/call via x402.

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": "sv_aml_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoOptional chain hint echoed in the result
entityNoOptional entity name for open-list name matching
addressNoSingle wallet address to screen
addressesNoComma-separated addresses, max 5

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/openWorld/non-destructive annotations, the description discloses fail-closed behavior ('unscreened' when the oracle cannot be reached), deterministic per-day reportId for audit dedup, batch limits and pricing, and the informational-only disclaimer. These are meaningful behavioral details an agent would not get from annotations alone.

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?

The description is front-loaded with the core purpose and packs many useful details into compact clauses. It is dense and semicolon-heavy rather than elegantly structured, but nearly every clause carries operational value and there is little pure filler.

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?

With no output schema, the description does a good job enumerating what the report contains: per-layer status and latency, name-match detail, address-format detection, and reportId. It also covers pricing, authentication, fail-closed behavior, and the informational-only limitation, leaving only minor gaps around exact response structure.

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 description coverage is 100%, so the baseline is 3, but the description adds value by specifying batch semantics for addresses (comma-separated, up to 5, same flat price) and by clarifying that entity is for open-list name matching. It does not elaborate much on chain beyond echoing, but it supplements the schema meaningfully.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope: an audit-grade sanctions screening report with per-layer status, name-match detail, address-format detection, and reportId. It implicitly distinguishes itself from the cheaper base verdict by saying it expands 'the $0.05 verdict', but it does not name the sibling tool sv_aml explicitly.

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?

It gives useful context that this is the audit-oriented, expanded report and supports batch screening up to five addresses at the same price, which implies when to choose it. However, it never explicitly says when to use this versus sv_aml or other screening tools, and it provides no explicit exclusions.

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.

Resources