Skip to main content
Glama

LIGHTHOUSE (МАЯК) — USDT freeze risk

Recent USDT freezes

list_recent_freezes
Read-onlyIdempotent

Log of executed blacklist operations, newest first: freezes (add), unfreezes (rem) or fund destructions (des), with address, chain, time, delay from proposal and amount. Requires sign-in.

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

Input Schema

NameRequiredDescriptionDefault
opNoOperation type, default add (freeze).
langNoLanguage of texts in the result. Default: Russian unless the client prefers English.
chainNoOptional chain filter.
limitNoDefault 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, non-destructive read. The description adds useful context beyond them: results are ordered newest first, they include delay-from-proposal and amount, and sign-in is required.

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?

One dense sentence, front-loaded with the resource and ordering, followed by the returned fields and the sign-in prerequisite. No sentence is wasted and nothing important is buried.

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?

With no output schema, the description compensates by listing the fields returned (address, chain, time, delay, amount). Combined with full schema coverage and annotations, an agent has enough to call it correctly, though the default limit and language behavior are only in the schema.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by spelling out all three operation semantics (add=freeze, rem=unfreeze, des=fund destruction) rather than only the default. It does not elaborate on the chain or language filters beyond the schema.

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?

The description names a specific resource (executed blacklist operations) and scope (newest first), and it distinguishes itself from proposal-oriented siblings by stating these are executed operations. An agent can tell this apart from list_open_proposals without opening either schema.

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 implied by the description of what is returned and the 'Requires sign-in' prerequisite, but there is no explicit guidance on when to choose this over list_open_proposals or get_freeze_statistics. The agent must infer the selection rule from sibling names alone.

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