Skip to main content
Glama
Sign In
lightningprox-mcp

lightningprox-mcp

by unixlamadev-spec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

check_balance

Retrieve the remaining sats, expiry date, and status of your configured Lightning spend token to verify prepaid access for pay-per-request model requests.

Instructions

Check the balance (sats), expiry and status of the configured spend token (LIGHTNINGPROX_SPEND_TOKEN).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool checks balance, expiry, and status, which implies a read-only operation. However, it does not explicitly state that it is non-destructive, does not describe any side effects, and does not mention authentication or rate limits. The description is adequate for a simple check but lacks richer behavioral context.

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 a single, front-loaded sentence that clearly states the tool's purpose. Every part of the sentence contributes useful information (what is checked, units, and the configuration variable), with no unnecessary wording.

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 (no parameters, no output schema, no annotations), the description provides sufficient context for an agent to understand its function. It might benefit from a brief note on what the returned 'status' entails or how it differs from get_token, but overall it is complete for a straightforward balance-checking operation.

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

Parameters4/5

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

The tool has zero parameters, so there is no parameter semantics to explain. The schema is empty with 100% coverage. The baseline score for zero parameters is 4, as the description need not add parameter meaning.

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 ('Check') and resource ('balance (sats), expiry and status of the configured spend token') with a concrete identifier (LIGHTNINGPROX_SPEND_TOKEN). It clearly communicates what is being checked, though it does not explicitly differentiate itself from the sibling tool get_token, which likely also deals with token information.

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?

Usage is implied: the tool is for checking the balance, expiry, and status of the already-configured spend token. There is no explicit guidance on when to use this versus alternatives like get_token, nor any mention of prerequisites or exclusions. Minimal viable guidance is present but could be improved.

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