Skip to main content
Glama
Sign In

Lightning Wallet

by io.github.lightningfaucet
OverviewDiscussionsAdmin

link_account

Link this operator to your Lightning Faucet account. Log in on lightningfaucet.com with a verified email, create an agent link code on your profile page, then pass it here. The code works once and expires in 15 minutes. Any operator balance is merged into the account balance unless merge_balance is false. Operator key required.

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": {
      "link_code": "<link_code>"
    },
    "name": "link_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
link_codeYesOne-time link code, XXXX-XXXX-XXXX-XXXX
merge_balanceNoDefault true

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does well: it discloses the one-time nature of the code, the 15-minute expiry window, the balance-merge side effect, and that an operator key is required. It stops short of describing what happens on failure or what the response contains, which matters for an account-linked mutation.

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 purpose, then the prerequisite flow, then the side effect and auth requirement. Four short sentences, each carrying information; only minor tightening is possible.

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 and no annotations, the description covers prerequisites, code lifetime, side effects, and auth requirements. Return value behavior is unstated, which is the main remaining gap for a linking operation whose success state an agent may need to report.

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 baseline would be 3, but the description adds real meaning: it explains where link_code comes from and the consequence of merge_balance ('any operator balance is merged into the account balance unless merge_balance is false'), which is more than the schema's bare 'Default true.'

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?

The description opens with a specific verb and resource: 'Link this operator to your Lightning Faucet account.' An agent knows exactly what the tool does. It does not, however, differentiate itself from the sibling link_user tool, leaving ambiguity about which linking tool to use.

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?

It gives a concrete precondition chain (log in on lightningfaucet.com with a verified email, create an agent link code on the profile page, then pass it here) and states the code is single-use with a 15-minute expiry. That's clear usage context, but it never names alternatives or when-not to use this versus link_user.

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