Skip to main content
Glama

LIGHTHOUSE (МАЯК) — USDT freeze risk

My monitored addresses

watchlist_list
Read-onlyIdempotent

List the user's addresses on LIGHTHOUSE monitoring with their current risk level, last check time and last level change. 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": "watchlist_list"
  }
}

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: the authentication requirement and the shape of the returned data (risk level, last check, last change), which the annotations do not convey.

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 tight sentences: the capability and its returned fields come first, the auth prerequisite second. No filler or redundancy.

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 read-only list tool with one optional parameter and no output schema, the description covers purpose, returned fields, and the sign-in requirement. Minor gaps remain around empty-list behavior or result size, but nothing essential to correct invocation 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?

There is a single optional 'lang' parameter with 100% schema description coverage including an enum and default behavior, so the schema does the work. The description adds nothing about language selection, which is acceptable at this coverage level but not value-adding.

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?

States a specific verb (List) and resource (the user's addresses on LIGHTHOUSE monitoring) and enumerates the returned fields: current risk level, last check time, last level change. This clearly separates it from the mutation siblings watchlist_add and watchlist_remove without needing to name them.

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 description implies the use case (viewing your own monitored addresses) and states the prerequisite 'Requires sign-in', but gives no explicit when-to-use versus alternatives such as check_addresses or check_address, and no exclusions. Usage is inferable but not spelled out.

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