Skip to main content
Glama

LIGHTHOUSE (МАЯК) — USDT freeze risk

My LIGHTHOUSE account

get_account
Read-onlyIdempotent

Show the signed-in user's LIGHTHOUSE plan, expiry dates, monitoring subscription and how many addresses are monitored. 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": "get_account"
  }
}

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the authentication requirement and by specifying the concrete fields returned, which the annotations cannot 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 returned-data summary is front-loaded and the precondition follows. No redundant restatement of the title or annotations, and every clause carries information.

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 usefully enumerates the returned fields and states the sign-in requirement, which is sufficient for a zero-required-parameter read tool. It does not say what happens when the user is not signed in (error vs empty), a minor remaining gap.

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?

The single lang parameter is fully documented in the schema, including its enum values and default behavior, so the schema already does the work. The description adds no further meaning about language selection, which matches the baseline-3 expectation at 100% schema coverage.

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?

Names a specific verb ('Show') and a precisely scoped resource ('the signed-in user's LIGHTHOUSE plan'), then enumerates the data returned: plan, expiry dates, monitoring subscription, and monitored address count. The 'signed-in user's' scope distinguishes it from catalog/order siblings such as get_plans and get_order without needing to open their schemas.

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?

Provides a real precondition ('Requires sign-in') that tells the agent when this tool is callable at all. It stops short of naming an explicit alternative (e.g. get_plans for the catalog of available plans) or a when-not condition, so it is clear context without 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