Skip to main content
Glama

LIGHTHOUSE (МАЯК) — USDT freeze risk

LIGHTHOUSE plans and payment methods

get_plans
Read-onlyIdempotent

List LIGHTHOUSE paid plans (API key with dashboard, webhooks and monitoring; or address monitoring only), prices in USDT and accepted crypto payment methods: USDT TRC-20 on Tron (always) and x402 USDC on Base (if enabled). Address checks are free; buy a plan when you need the REST API at scale, open freeze proposals or monitoring.

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

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

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description adds value by disclosing the payment-method matrix — USDT TRC-20 on Tron is always available, x402 USDC on Base only "if enabled" — which is real conditional behavior an agent cannot infer from structured fields. It omits caching or freshness of pricing, hence not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, with pricing/payment detail and then usage context following in a logical order. The parenthetical plan description is dense but each clause carries information; only the final sentence is slightly indirect about what this tool does versus what the agent should do next.

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 substitutes by describing the return contents (plans, prices, payment methods) and the conditional availability of x402. For a single optional-parameter read-only listing this is nearly sufficient; only the `lang` parameter goes unmentioned.

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 description coverage is 100% and the single optional `lang` enum is fully documented in the schema, including the default-to-Russian rule. The description says nothing about language selection, so the baseline 3 applies — the schema does all the parameter work.

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?

Opens with a specific verb+resource ("List LIGHTHOUSE paid plans") and enumerates the returned content: plan tiers, USDT prices, and accepted crypto payment methods. The agent can distinguish this from order/payment siblings (create_order, submit_payment) by the retrieval nature of the call, though no sibling is named explicitly.

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?

"Address checks are free; buy a plan when you need the REST API at scale, open freeze proposals or monitoring" gives the agent a clear trigger context: consult plans when the free path or existing access is insufficient. It stops short of naming concrete alternatives such as check_address or create_order, so routing is implied rather than stated.

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