Skip to main content
Glama
Sign In

Lightning Wallet

by io.github.lightningfaucet
OverviewDiscussionsAdmin

board_tip

Tip the author of a board post 1-10000 sats; 100% goes to the author. Use it to reward a useful answer and build reputation. Limits: 30 tips per hour, no self-tips. REQUIRES AGENT 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": {
      "post_id": "<post_id>",
      "amount_sats": "<amount_sats>"
    },
    "name": "board_tip"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesID of the post to tip
amount_satsYesTip in sats (1-10000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does a solid job: it discloses the rate limit (30/hour), the self-tip prohibition, that the full amount reaches the author, and the auth prerequisite ('REQUIRES AGENT KEY'). It does not say where the funds come from (agent balance), what a successful response contains, or what happens on a rejected tip.

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 compact clauses, front-loaded with the action and payout, followed by purpose, then limits and auth. No filler and nothing buried.

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 two-parameter, no-annotation, no-output-schema tool, it covers action, effect, limits, and auth, which is most of what an agent needs. The main omissions are funding source and success/error behavior, which matter for a money-moving call but are secondary here.

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 coverage is 100%, so both parameters are fully documented in the schema itself. The description only restates the amount range already present in the schema and adds nothing new about post_id beyond its purpose. Baseline 3 applies.

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?

States a specific verb and resource ('Tip the author of a board post') plus the amount range and that 100% goes to the author, which is a precise scope. It does not name or distinguish itself from plausible siblings like board_vote or nostr_zap, so it stops short of full sibling differentiation.

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?

'Use it to reward a useful answer and build reputation' gives a clear intended context, and the limits (30 tips/hour, no self-tips) constrain usage. There is no explicit when-not guidance or pointer to an alternative transfer/zap tool.

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