Skip to main content
Glama

LIGHTHOUSE (МАЯК) — USDT freeze risk

USDT blacklist statistics

get_freeze_statistics
Read-onlyIdempotent

Current statistics of the USDT blacklist across all chains: number of blacklisted addresses, frozen USDT, freezes in the last 24 h / 30 days, open freeze proposals, median delay from proposal to freeze by chain, delay distribution and monthly dynamics for the last 12 months.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_freeze_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of texts in the result. Default: Russian unless the client prefers English.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real context: the data is a present-moment snapshot spanning all chains with a fixed 12-month lookback window, which tells the agent there is no historical or per-chain scoping available.

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 sentence with the resource front-loaded and the metric list following a colon, so an agent can stop reading early once it has matched the purpose. The enumeration is long but each item carries information, particularly since no output schema exists.

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?

Because there is no output schema, the metric enumeration is essential and it is present, covering counts, volumes, time windows, proposal state, and delay analytics. Minor gaps remain around whether values are cached or live and how the delay distribution is shaped, but nothing blocks a correct invocation.

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?

There is only one optional parameter (lang) and the schema documents it fully at 100% coverage, including the enum and the Russian-default behavior. The description adds nothing about it, which is acceptable given the schema does the work, but no extra meaning is contributed.

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 names a specific resource (USDT blacklist) and a specific operation type (aggregate statistics across all chains), then enumerates the exact metrics returned. This clearly separates it from listing siblings such as list_recent_freezes or list_open_proposals, though it never names those alternatives explicitly.

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?

Usage is only implied: an agent can infer this is the dashboard-style aggregate rather than a raw event listing. There is no explicit when-to-use statement, no mention of when to prefer list_recent_freezes or list_open_proposals, and no note about refresh cadence for what is labeled 'current'.

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