Skip to main content
Glama

LIGHTHOUSE (МАЯК) — USDT freeze risk

Order status and API key

get_order
Read-onlyIdempotent

Get the status of a LIGHTHOUSE order (pending, paid, expired). When paid, returns the API key (for api plans) or the monitoring expiry (for watch plans). Checks incoming transfers on each call.

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": {
      "order_id": "<order_id>"
    },
    "name": "get_order"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context: it checks incoming transfers on every call (implying latency and a live network dependency) and conditionally returns an API key or monitoring expiry depending on plan type.

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?

Three short sentences, front-loaded with the core action and result, with no redundant wording. Each sentence adds distinct information (states, conditional returns, per-call transfer check).

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 does the work of explaining return values (API key vs monitoring expiry) and the state set, which is adequate for a simple two-parameter read tool. The only real gap is the undocumented order_id format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: lang is documented in the schema, but the required order_id has no description anywhere. The description never explains the order_id format or where it comes from, so it fails to compensate for the coverage gap on the one mandatory parameter.

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 and resource ('Get the status of a LIGHTHOUSE order') and enumerates the possible states (pending, paid, expired), plus what is returned in the paid case. An agent can distinguish this from create_order without opening the schema.

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?

Usage is implied by the name and the returned states, but there is no explicit when-to-use or when-not guidance and no named alternative (e.g., create_order for new orders). The agent must infer the context.

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