Skip to main content
Glama

Veriql freeze check

veriql_freeze

Check whether Tether or Circle has frozen an EVM or Tron address by reading the issuer's contract directly, and see if it received USDT from a Tether-frozen address.

Instructions

Has Tether or Circle frozen this address, read straight off the issuer's contract, and did it receive USDT directly from an address Tether froze (exposure, not guilt). EVM and Tron. Free, no key needed.

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_freeze"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesEVM or Tron address

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?

No annotations are provided, so the description carries the full burden, and it does well: it names the authoritative data source (the issuer's contract, not a heuristic), states supported chains (EVM and Tron), declares the call free with no API key, and pre-empts the most likely misreading by framing the second signal as exposure rather than guilt. It stops short of describing the response shape or the handling of an unchecked address.

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?

A single compact sentence followed by two fragments, front-loaded with the core question and then the qualifier. Every clause carries information: source of truth, scope of the second signal, chain support, and cost. Nothing is padded.

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 one-parameter lookup with no annotations and no output schema, the description covers the data source, the chain scope, the two distinct signals returned, and the cost/authentication model. What remains thin is the return format, which the description does not address, and behavior for addresses the issuer never touched.

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?

The schema already documents the single parameter ('EVM or Tron address') at 100% coverage, so the baseline would be 3. The description reinforces the accepted address families, which is the only real ambiguity for this parameter. With only one parameter and complete schema coverage, there is little more to add.

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 gives a specific verb and resource: it reports whether Tether or Circle has frozen an address, read directly from the issuer's contract, and whether the address received USDT from a Tether-frozen address. This is clear. The parenthetical 'exposure, not guilt' also clarifies the nature of the secondary flag. It does not explicitly name a sibling or say how it differs from a broader screening tool such as batch_screen, so it falls short of 5.

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?

The phrase 'Free, no key needed' and the chain coverage ('EVM and Tron') give practical context for when this call is convenient. 'Exposure, not guilt' signals how to interpret the result. However, there is no explicit statement of when to choose this over alternatives, such as a full screen or a counterparty check, and no described preconditions.

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