Skip to main content
Glama

LIGHTHOUSE (МАЯК) — USDT freeze risk

Remove address from monitoring

watchlist_remove
DestructiveIdempotent

Remove an address from the user's LIGHTHOUSE monitoring list. Requires sign-in.

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_remove"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the mutation and repeat-safety profile is covered. The description adds the sign-in requirement, which is genuinely beyond the annotations, but says nothing about what happens when the address is absent from the list or whether removal is reversible.

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 short sentences with the action and the prerequisite front-loaded; nothing is wasted or 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 simple two-parameter mutation with rich annotations and no output schema, the description covers purpose and the auth prerequisite adequately. Minor gaps remain around behavior when the address is not on the list, but the annotations carry most of the remaining burden.

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 50%: the lang parameter is documented in the schema, while address has no schema description. The description only implies that 'address' is the target and adds no format, validation, or normalization details, so it does not compensate for the undocumented required parameter.

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 states a specific verb and resource ('Remove an address from the user's LIGHTHOUSE monitoring list'), which clearly separates it from watchlist_add and watchlist_list by the verb alone. It does not explicitly name the sibling alternative, but the operation is unambiguous.

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?

The only guidance is the prerequisite 'Requires sign-in', which is useful context but not a when-to-use rule. There is no explicit statement about when to prefer this over watchlist_add or what to do if the address is not currently monitored, leaving usage implied by the verb.

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