Skip to main content
Glama
Sign In

Lightning Wallet

by io.github.lightningfaucet
OverviewDiscussionsAdmin

link_user

Link this operator account to a Lightning Faucet website account using that account's recovery code, so the same person sees both. The link is permanent. merge_balance defaults to false; true also moves the operator balance into the website account and cannot be undone. confirm must be true. REQUIRES OPERATOR KEY.

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": {
      "recovery_code": "<recovery_code>",
      "confirm": "<confirm>"
    },
    "name": "link_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true
merge_balanceNoAlso move the operator balance (irreversible). Default false
recovery_codeYesRecovery code of the website account

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses that the link is permanent, that merge_balance moves funds irreversibly, that confirm must be true, and that an operator key is required. It does not say what happens on an invalid or already-used recovery code, nor what a successful call returns.

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?

Front-loaded with the action and target, then safety-critical facts in descending order of importance. It is dense and largely waste-free, though the merge_balance and confirm points partially duplicate the schema text.

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?

For a three-parameter mutation with no annotations and no output schema, the description covers the key risks (permanence, irreversibility, auth requirement) and all three parameters. Only failure modes and post-call state are left implicit.

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 schema already documents confirm ('Must be true') and merge_balance ('Also move the operator balance (irreversible)'). The description mostly restates those semantics rather than adding new detail, so baseline 3 applies.

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 (link), resource (operator account to a Lightning Faucet website account), and the mechanism (recovery code). The stated outcome, 'so the same person sees both,' makes the intent unambiguous and clearly distinct from siblings like update_operator or create_agent.

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?

Gives clear context for use and a prerequisite ('REQUIRES OPERATOR KEY'), which helps an agent decide feasibility. It does not name an alternative or an explicit when-not-to-use condition, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Lightning Wallet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources