Skip to main content
Glama
Sign In
Lightning Wallet MCP

Lightning Wallet MCP

by lightningfaucet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_budget

Set or update an agent's spending budget in satoshis. Define a budget limit or allow unlimited spending by setting zero. Requires operator authorization.

Instructions

Set or update budget limit for an agent. 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": {
      "agent_id": "<agent_id>",
      "budget_limit_sats": "<budget_limit_sats>"
    },
    "name": "set_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesAgent ID to update
budget_limit_satsYesNew budget limit in sats (0 for unlimited)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.9

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds the operator key requirement but does not detail other behavioral aspects like idempotency, merging vs overriding, or error conditions, which would be helpful for a mutation tool.

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 extremely concise—two sentences with zero wasted words. The critical requirement is front-loaded, and every sentence adds value. This is a model of efficient communication.

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?

Given the tool's simplicity (two parameters, no output schema, no annotations), the description covers the essential use case and the operator key requirement. It lacks details on return values or error scenarios, but these are not critical for a straightforward set operation.

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?

The input schema covers both parameters with full descriptions (100% coverage). The description adds no additional semantic value beyond what the schema provides, so a baseline score of 3 is appropriate.

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 clearly states the action ('Set or update budget limit') and the target resource ('an agent'), making the tool's purpose unambiguous. It distinguishes itself from sibling tools like get_budget_status, which is a read operation.

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?

The description mentions a critical prerequisite ('REQUIRES OPERATOR KEY'), which guides the agent on when the tool can be used. However, it does not explicitly state when not to use it or provide alternatives for budget-related queries, leaving room for improvement.

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

Deploy Server

Other Tools