Skip to main content
Glama

LIGHTHOUSE (МАЯК) — USDT freeze risk

Add address to monitoring

watchlist_add
Idempotent

Put an address on LIGHTHOUSE monitoring (up to 10 per account). Risk is re-checked every 10 minutes and right after Tether multisig events; the user gets a Telegram or e-mail notification when the level changes. Requires sign-in and an active monitoring subscription or LIGHTHOUSE plan.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of texts in the result. Default: Russian unless the client prefers English.
noteNoOptional label, e.g. 'hot wallet'.
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the quota (10 per account), the re-check cadence (every 10 minutes and after Tether multisig events), the notification channels (Telegram or e-mail on level change), and the auth/subscription prerequisites. These are exactly the operational facts an agent cannot infer from the readOnly/idempotent/destructive hints.

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?

Two sentences, front-loaded with the action, then quota, monitoring cadence, notification behavior, and prerequisites in a compact sequence. No sentence is filler and nothing essential 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?

For a small mutation tool with annotations covering safety and no output schema, the description supplies prerequisites, limits, and post-add behavior. It does not say what happens when the 10-address cap is already reached or what the success response contains, which are minor residual gaps.

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 coverage is 67%, so the schema already documents the lang enum, the note label with its maxLength, and the required address. The description only implies the address parameter through 'Put an address' and adds no further meaning for note or lang, leaving it at the baseline for partially documented schemas.

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 opens with a specific verb and resource: 'Put an address on LIGHTHOUSE monitoring,' which is unambiguously an add operation. It does not explicitly contrast itself with watchlist_list or watchlist_remove, but the verb alone makes the intent distinct from those siblings.

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?

It gives clear preconditions for use: sign-in is required and an active monitoring subscription or LIGHTHOUSE plan is needed, plus a per-account cap of 10. It stops short of naming an alternative tool or stating when-not to use this one, so it is clear context without explicit exclusions.

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