bolthub

Official

Overview Schema Source Related Servers Discussions Admin

node_status

Check a deployed Lightning node's status and block until it reaches a specified milestone, such as wallet creation or becoming payable, eliminating manual polling.

Instructions

Check the status of a deployed Lightning node. Returns current state, IP address, sync progress, and setup instructions when applicable. Pass wait_for to BLOCK until a milestone is reached (for driving deploy → wallet → bind without babysitting): the call polls server-side state and returns as soon as the condition holds, errors loudly on timeout or a terminal state, and stops immediately when only user action can progress things (wallet creation is a browser step). Never wrap this tool in your own polling loop — use wait_for.

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": {
      "node_id": "<node_id>"
    },
    "name": "node_status"
  }
}

Input Schema

Name	Required	Description
`node_id`	Yes	Node ID returned by deploy_node
`wait_for`	No	Block until: wallet_pending = VPS up, LND waiting for its wallet (next step is the user's seed ceremony); ready = wallet created and macaroon minted; payable = ready AND an active channel with inbound capacity (what a settlement test needs). A node already past the milestone returns immediately.
`timeout_s`	No	Hard wait ceiling in seconds, 5-600 (default 120). On timeout the tool errors with what to do next; it never silently keeps polling.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.2Jul 15, 2026

addedInput schema / properties / timeout_s

Added value: +{
+  "description": "Hard wait ceiling in seconds, 5-600 (default 120). On timeout the tool errors with what to do next; it never silently keeps polling.",
+  "type": "number"
+}

addedInput schema / properties / wait_for

Added value: +{
+  "description": "Block until: wallet_pending = VPS up, LND waiting for its wallet (next step is the user's seed ceremony); ready = wallet created and macaroon minted; payable = ready AND an active channel with inbound capacity (what a settlement test needs). A node already past the milestone returns immediately.",
+  "enum": [
+    "wallet_pending",
+    "ready",
+    "payable"
+  ],
+  "type": "string"
+}

First observedv0.1.0Jul 12, 2026

TDQS

A5/5.0

Behavior5/5

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

No annotations provided, so description fully details behavior: blocks server-side, errors on timeout/terminal state, stops when only user action needed (wallet creation). This is comprehensive.

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?

Every sentence is informative; the description is front-loaded with the core purpose, then details on wait_for. No redundancy or fluff.

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

Completeness5/5

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

For a 3-parameter tool with no output schema, the description fully covers what the tool returns and all parameter behaviors, making it self-contained for correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and description adds significant context: explains each wait_for enum value, timeout range and behavior, and the return value implications for node_id.

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 tool's purpose: checking the status of a deployed Lightning node, returning specific fields like state, IP, and sync progress. It differentiates from sibling tools like deploy_node by focusing on status retrieval.

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

Usage Guidelines5/5

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

Explicit guidance not to wrap in own polling loop and to use wait_for for blocking. Clearly explains when to use each wait_for option and the timeout behavior.

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