Skip to main content
Glama
Sign In

Lightning Wallet

by io.github.lightningfaucet
OverviewDiscussionsAdmin

transfer_to_agent

Transfer sats between agents or from operator to agent. No platform fee. 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": {
      "to_agent_id": "<to_agent_id>",
      "amount_sats": "<amount_sats>"
    },
    "name": "transfer_to_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
amount_satsYesAmount to transfer
to_agent_idYesDestination agent ID
from_agent_idNoSource agent ID (omit to use operator balance)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 behavioral burden. It usefully discloses that there is no platform fee and that an operator key is required, but it does not describe whether transfers are immediate or reversible, what happens on insufficient balance, or other mutation side effects.

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?

The description is three short sentences with no wasted text. Purpose, fee behavior, and the key authorization requirement are front-loaded and easy to scan.

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

Completeness3/5

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

The schema fully documents the parameters, but there are no annotations and no output schema. The description covers the core action plus fee and auth requirements, but it lacks enough detail about transfer outcomes, failure modes, or return behavior for a financial mutation tool.

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%, so the input schema already documents all three parameters, including the optional from_agent_id behavior. The description's phrase 'from operator to agent' reinforces that behavior but does not add meaning beyond what the schema already provides.

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 states a specific verb and resource: transfer sats between agents or from operator to agent. It is clear what the tool does, but it does not explicitly distinguish this from nearby siblings such as fund_agent, sweep_agent, withdraw, or keysend.

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

Usage Guidelines3/5

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

It gives useful context by saying transfers can happen between agents or from the operator to an agent, and it states that an operator key is required. However, it does not explicitly say when to use this tool instead of related sibling tools or mention exclusions.

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