Skip to main content
Glama

Veriql payee check

veriql_payee

Checks whether a crypto address is OFAC-sanctioned, on Drain Watch, or frozen by Tether or Circle before you send funds. Returns do_not_pay, no_known_risk, or incomplete across EVM, Bitcoin, Solana and Tron.

Instructions

Before sending money to an address: is it OFAC-sanctioned, on Drain Watch, or frozen by Tether or Circle (funds sent there can never leave). Answers do_not_pay, no_known_risk or incomplete, and incomplete is not a clean result. EVM, Bitcoin, Solana, Tron.

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": {
      "address": "<address>"
    },
    "name": "veriql_payee"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe address you are about to pay

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it enumerates the possible result states (do_not_pay, no_known_risk, incomplete) and warns that incomplete is not a clean result — a critical behavioral caveat an agent would otherwise misread. It also notes the consequence of paying a frozen address. It omits cost, rate limits, and latency, keeping it from a 5.

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?

Front-loaded with the decision context, then the risk categories, then the return states, then chains — a sensible order with no filler. The trailing chain list is a bare fragment, which is efficient but slightly telegraphic.

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 lookup with no output schema, the description supplies what matters: supported chains, the outcome vocabulary, and the interpretation trap around 'incomplete'. Adding the alternative for bulk screening would make it fully complete.

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?

Only one parameter with 100% schema coverage, so the schema already explains 'address'. The description adds genuine meaning by tying it to 'the address you are about to pay' and by enumerating supported chains (EVM, Bitcoin, Solana, Tron), which the schema does not state.

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?

Names a specific question answered about a specific resource: whether an address is OFAC-sanctioned, on Drain Watch, or frozen by Tether/Circle. This is clearly an address risk screen, distinguishable from siblings like veriql_token or veriql_deployer.

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?

'Before sending money to an address' gives an explicit trigger context, which is the key usage guidance an agent needs. It stops short of naming alternatives such as veriql_batch_screen for screening multiple addresses, so the when-not guidance is incomplete.

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