Skip to main content
Glama

Veriql USDT pre-send check

veriql_send

Checks whether a planned USDT transfer on Tron or Ethereum will go through and whether the recipient is sanctioned or frozen, returning do_not_send, will_fail, may_fail, goes_through, or incomplete.

Instructions

Before sending USDT on Tron or Ethereum: will this transfer go through (frozen sender, unactivated account, too little USDT, too little TRX or ETH for the fee, a contract that refuses it, read off the chain with the exact fee), and should it go there at all (recipient OFAC-sanctioned, on Drain Watch, or frozen by Tether, where USDT arrives and can never leave). Answers do_not_send, will_fail, may_fail, goes_through or incomplete, and 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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "veriql_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe recipient, on the same chain
fromYesThe sending address (Tron T... or Ethereum 0x...)
amountNoUSDT to send, like 250 or 12.5; leave out to check the whole balance

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A3.9/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 well: it discloses that data is read off the chain with the exact fee, enumerates the failure causes it detects (frozen sender, unactivated account, insufficient balance, fee shortfall, refusing contract, sanctions/Drain Watch/Tether freeze), and names the five possible verdicts. It omits latency, rate limits, and whether the call is strictly read-only, which is implied but not stated.

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?

A single dense sentence, but front-loaded with the operative trigger and with the two concerns (will it go through / should it go there) clearly separated. The long parenthetical risk lists are informative rather than padding, though they make it heavier than necessary.

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?

There is no output schema, so the description must convey return values, and it does by naming the five verdicts and warning that 'incomplete' is not a clean result. It could say more about what accompanies a verdict (per-cause reasons, fee figure), leaving a small gap for a three-parameter decision tool.

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%, so the schema already documents 'to', 'from' (including address formats) and the optional 'amount' with its whole-balance behavior. The description adds no parameter-level detail beyond that baseline, which is acceptable given complete schema coverage.

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?

States a specific check performed against a specific asset and chains ('Before sending USDT on Tron or Ethereum'), covering both executability and recipient risk. An agent can tell this is a single-transfer pre-send simulation, distinct in scope from screening or batch tools, though no sibling is named explicitly.

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?

The trigger condition is explicit and front-loaded: use it before sending USDT. It gives no exclusions or named alternatives (e.g. when to prefer a batch screen or a generic preflight), so an agent must infer the boundary cases.

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