Skip to main content
Glama
signaltech-org

bolthub

Official
by signaltech-org
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

deploy_node

Guides users through choosing a VPS provider and region, then deploys a non-custodial Lightning node (LND + Neutrino) on their own server.

Instructions

Deploy a Lightning node (LND + Neutrino) on the user's own VPS — fully non-custodial. GUIDED FLOW, call it repeatedly as the conversation progresses: (1) no arguments → provider menu with prices; (2) provider chosen but no credential stored → sign-up + access-token steps for that provider (the token itself is entered at bolthub.ai/nodes/deploy in the browser, never in chat); (3) credential present → region menu; (4) region → server sizes with monthly prices; (5) region + size (or size 'recommended') → deploys and returns the node id. The user then creates the wallet + seed phrase on their own node page; bind it as the payout wallet afterwards with connect_wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
torNoEnable Tor-only mode for maximum privacy. Default: false.
sizeNoServer size slug from the sizes step, or 'recommended' for the cheapest (a Lightning node runs fine on it). Deploy starts only when both region and size are given.
regionNoRegion slug from the region menu step.
api_keyNoDEPRECATED: passing a VPS key here puts it into chat context, and agent sessions can't store keys anyway. The tool walks the user through adding it at bolthub.ai/nodes/deploy instead.
providerNoChosen provider. Omit to get the provider menu with prices.
credential_idNoStored VPS credential id. Omit when the account has exactly one (it's used automatically); the tool lists them when there are several.

Tool Definition Quality

A5/5.0
Behavior5/5

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

The description fully discloses the guided flow, the need for user to enter token at a website, and that deployment yields a node id. It aligns with annotations (non-destructive, open world).

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 structured with numbered steps, each sentence adds essential detail for the guided flow, and it is concise given the complexity.

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?

Despite lacking an output schema, the description states the result (node id) and covers all phases, leaving no ambiguity for the agent.

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?

All 6 parameters are described in schema and the description adds rich context: e.g., provider omitted for menu, credential_id automatic when one, meaning of 'recommended' size.

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 deploys a Lightning node (LND+Neutrino) on the user's own VPS and details the guided multi-step flow, distinguishing it from siblings like connect_wallet and node_status.

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?

It explicitly describes when to call repeatedly as the conversation progresses, when to omit parameters (e.g., omit provider for menu), and references connect_wallet for post-deployment binding.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/signaltech-org/bolthub-sdk'

If you have feedback or need assistance with the MCP directory API, please join our Discord server