Skip to main content
Glama

LIGHTHOUSE (МАЯК) — USDT freeze risk

Open Tether freeze proposals

list_open_proposals
Read-onlyIdempotent

List freeze (addBlackList) and unfreeze proposals that are open in Tether multisigs but not yet executed — the early-warning signal before an address is frozen. Each item has address, chain, signatures collected/required, age, probability of execution within 10 min and 1 h, and USDT amount at risk. 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_open_proposals"
  }
}

Input Schema

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

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 establish read-only, idempotent, non-destructive, open-world behavior, so the description is not required to restate safety. It adds genuinely new context the annotations cannot convey: a sign-in requirement and the exact per-item payload (address, chain, signatures collected/required, age, execution probabilities at 10 min and 1 h, USDT at risk), which is important since there is no output schema.

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?

Two sentences, front-loaded with the core definition and ending with the operational prerequisite. The field enumeration sentence is dense but every listed field earns its place because no output schema exists to carry that information.

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?

For a two-optional-parameter read-only list tool with no output schema, the description supplies everything the agent needs: what is returned field-by-field, what 'open' means, the auth prerequisite, and the analytical value of the result. Nothing material is missing.

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 description coverage is 100% and both parameters are enumerated with their own descriptions, so the schema does the heavy lifting. The description adds nothing about 'lang' or 'chain' semantics, putting it at the baseline for fully documented schemas.

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 verb and resource (freeze/unfreeze proposals in Tether multisigs) and bounds the scope precisely with 'open ... but not yet executed', which cleanly separates it from siblings like list_recent_freezes and get_freeze_statistics. It also names the underlying operation (addBlackList) and frames the entire tool as an 'early-warning signal', giving the agent a clear mental model.

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?

Usage context is stated clearly: this is the forward-looking view of pending freezes, i.e. the thing to call when you want warning before an address is frozen. No explicit exclusion or named alternative is given (e.g. it never says to use list_recent_freezes for already-executed freezes), so the agent must infer the boundary 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