Skip to main content
Glama

LIGHTHOUSE (МАЯК) — USDT freeze risk

Buy a LIGHTHOUSE plan with crypto

create_order

Create an order for a LIGHTHOUSE plan paid in crypto. payment_method=usdt_trc20 (default): returns the Tron address and the exact USDT amount (unique cents identify the order), valid 60 minutes; after sending, call submit_payment with the tx hash, then get_order returns the API key. payment_method=x402: returns x402 v2 PaymentRequired (USDC on Base); retry the same call with the signed payload in _meta["x402/payment"] and the API key is returned immediately. Without sign-in the key is not linked to an account; extend=true requires sign-in; monitoring needs the key to be linked to an account. Never send funds without the user's explicit approval.

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": {
      "plan": "<plan>"
    },
    "name": "create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of texts in the result. Default: Russian unless the client prefers English.
planYesapi30: 30 days, api365: 1 year. Both include an API key, dashboard, webhooks and monitoring of up to 10 addresses (monitoring needs sign-in).
extendNoExtend the signed-in user's existing API key instead of issuing a new one.
payment_methodNoDefault usdt_trc20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and non-idempotent, but the description adds substantial behavior they cannot carry: the 60-minute payment window, the unique-cents amount-matching scheme, the x402 v2 retry mechanics, and the fact that an unauthenticated key is not linked to an account. What is missing is what happens on expiry or payment mismatch; the non-idempotent retry path for x402 could also be spelled out more explicitly.

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?

Dense and front-loaded, with the payment flow stated before caveats, and every clause carries operational content including the safety instruction never to send funds without user approval. The semicolon-chained single paragraph makes the two payment rails harder to scan than a short bullet structure would.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by describing returned artifacts for both rails (Tron address plus exact USDT amount; x402 PaymentRequired; API key on success). Combined with auth requirements and the follow-up tool sequence, an agent has everything needed to invoke and continue this flow correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description goes beyond it by explaining what each payment_method value produces end-to-end and by tying extend=true to a sign-in requirement. plan and lang semantics are left entirely to the schema, which is acceptable given full 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?

States a specific verb and resource ('Create an order for a LIGHTHOUSE plan paid in crypto') and immediately scopes the two payment rails it supports. An agent can distinguish it from get_order, submit_payment and get_plans without opening any schema, because the description names the actual post-creation steps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit branching per payment_method: usdt_trc20 (default) returns a Tron address and exact amount and is followed by submit_payment then get_order; x402 returns PaymentRequired and is retried with the signed payload in _meta['x402/payment']. It also states preconditions (extend=true and monitoring both require sign-in) and which sibling tool to call next at each step.

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