Skip to main content
Glama

LIGHTHOUSE (МАЯК) — USDT freeze risk

Submit a USDT payment for an order

submit_payment
Idempotent

After sending USDT TRC-20 for an order, pass the order_id and the Tron transaction hash. The service finds the transfer on-chain, checks recipient and exact amount and, once confirmed (~1 minute), issues or extends the API key. Returns a verdict: paid, unconfirmed, wrong_amount, wrong_recipient or not_found.

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>",
      "tx_hash": "<tx_hash>"
    },
    "name": "submit_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of texts in the result. Default: Russian unless the client prefers English.
tx_hashYesTron transaction id, 64 hex characters.
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses the side effect (issuing or extending the API key), the on-chain verification steps (recipient and exact amount), the ~1 minute confirmation latency, and the complete set of possible verdicts. That is substantive behavioral context an agent cannot infer from readOnlyHint/openWorldHint/idempotentHint alone, and nothing conflicts with them.

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 tightly packed sentences ordered as precondition, mechanism, and return values, with no filler. The single most important fact, that the transfer must already have been sent, is front-loaded.

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, describing the five verdict values is exactly the right compensation, and latency plus side effects are covered. It omits retry/re-submission guidance for the non-paid verdicts, which is the main remaining gap for a tool with this outcome branching.

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 67%, so the description must carry some weight: it explains that tx_hash is used by the service to locate the transfer on-chain and frames order_id as the order the payment settles, which is more than the bare schema (order_id has no schema description at all). The lang parameter's role is left entirely to the schema.

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?

The description names a concrete operation: verifying an on-chain USDT TRC-20 transfer for an order and issuing/extending the API key based on the verdict. That makes it clearly distinct from siblings such as create_order and get_order, which handle order lifecycle rather than payment settlement.

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?

'After sending USDT TRC-20 for an order, pass the order_id and the Tron transaction hash' establishes the precondition and correct moment to call it. It stops short of guidance for the failure branches (e.g. what to do on 'unconfirmed' or 'not_found'), and no alternative tool is named.

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