Skip to main content
Glama

LIGHTHOUSE (МАЯК) — USDT freeze risk

Check USDT freeze risk

check_address
Read-onlyIdempotent

Check available signals of a USDT (Tether) freeze. Covers Ethereum, Tron, Avalanche, Celo, Solana and TON. Returns risk level 0–3 (0 no signals found, not a safety guarantee; 1 freeze proposal open; 2 second of three signatures; 3 evidence of a freeze), recommended manual review, per-chain reasons and freshness, USDT balance, open proposals and past episodes. Timing, completeness and future execution are not guaranteed. Use for counterparty due diligence or checking whether an address has freeze signals. Does not authorise or perform asset operations.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of texts in the result. Default: Russian unless the client prefers English.
liveNoAlso read status and balance from a node right now (default true). false is faster.
addressYesAddress: 0x… (Ethereum/Avalanche/Celo), T… (Tron), TON (EQ…/UQ…) or Solana base58.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, the description defines the full risk-level scale (0–3) with semantics for each level, warns that level 0 is 'not a safety guarantee,' and discloses that 'timing, completeness and future execution are not guaranteed.' It also reports what data accompanies the result (per-chain reasons and freshness, USDT balance, open proposals, past episodes), which is exactly the behavioral context annotations cannot carry.

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?

Purpose is front-loaded in the first sentence, followed by scope, the return contract, caveats, and use cases in a logical order. The parenthetical risk-level list is dense but each clause carries distinct information; no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 describe returns — and it does, defining the 0–3 risk scale, the manual-review recommendation, and the accompanying evidence fields. Combined with the explicit limitations and the safety disclaimer, an agent has everything needed to call and interpret this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: the chain enumeration clarifies which address formats and networks are in scope, and the 'timing, completeness' caveat contextualizes the 'live' flag's tradeoff of freshness vs speed. The only mild gap is that the 'lang' enum's effect is already fully covered by the schema.

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 verb and resource ('Check available signals of a USDT (Tether) freeze') and enumerates the supported chains (Ethereum, Tron, Avalanche, Celo, Solana, TON), so the agent knows exactly what is being evaluated. It does not explicitly contrast itself with the sibling 'check_addresses' (plural), but the singular-address scope is clear from the required 'address' parameter.

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 an explicit use case: 'Use for counterparty due diligence or checking whether an address has freeze signals,' and a negative boundary: 'Does not authorise or perform asset operations.' It stops short of naming alternatives (e.g. the plural check_addresses for batch screening) or stating when not to rely on the result, so it is clear context without full routing guidance.

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