Skip to main content
Glama

Veriql batch address screen

veriql_batch_screen

Screen up to 50 EVM, Tron, Solana, or Bitcoin addresses in one call for OFAC sanctions, Drain Watch, and Tether/Circle freezes, returning do_not_pay, no_known_risk, or incomplete status.

Instructions

Screen up to 50 addresses in one call against OFAC SDN sanctions, Drain Watch and Tether and Circle freezes (EVM and Tron). For payout runs, token holder lists and sniper wallets. Each address gets do_not_pay, no_known_risk or incomplete; incomplete is not a clean result.

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": {
      "addresses": "<addresses>"
    },
    "name": "veriql_batch_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressesYes1 to 50 EVM, Tron, Solana or Bitcoin addresses

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and it does disclose the important parts: the 50-address cap and the three-valued outcome (do_not_pay / no_known_risk / incomplete) with the warning that incomplete is not clean — genuinely useful output semantics since no output schema exists. It says nothing about auth/cost, rate limits, or what happens on a partially invalid batch (does the whole call fail?), which are real gaps for a screening tool.

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?

Three short sentences, front-loaded with capability then use cases then result semantics; almost no waste. The middle sentence is a fragment, but it still carries distinct information.

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?

For a single-parameter batch tool with no output schema, the description covers what is screened, the batch bound, and the meaning of every possible verdict. Only failure/partial-failure behavior remains undocumented.

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?

One parameter at 100% schema coverage, so the baseline is 3; the description's 'up to 50 addresses' merely restates the schema's '1 to 50'. The parenthetical '(EVM and Tron)' attached to the freeze sources is ambiguous against the schema's 'EVM, Tron, Solana or Bitcoin', leaving the agent unsure whether non-EVM/Tron addresses are partially screened.

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?

Names a specific verb (screen) and resource (addresses) plus batch scope (up to 50 in one call) and the exact data sources checked (OFAC SDN, Drain Watch, Tether/Circle freezes). It does not explicitly contrast itself with the closest sibling (veriql_scan), so an agent must infer the single-vs-batch split rather than being told.

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

Usage Guidelines4/5

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

Gives concrete usage contexts — payout runs, token holder lists, sniper wallets — which is more than most definitions offer. It stops short of exclusions or naming an alternative tool for single-address checks, so routing guidance is implied rather than explicit.

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