Skip to main content
Glama

CoinVet

Check a Lightning address / LNURL resolves

lightning_address_check
Read-onlyIdempotent

Resolve a Lightning address (user@domain) or bech32 LNURL to its LNURL-pay endpoint and return whether it is valid, min/max sendable sats, comment length, Nostr zap support and description. Never requests an invoice or pays. Also recognizes BOLT11 invoices.

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": {
      "address": "<address>"
    },
    "name": "lightning_address_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesLightning address (user@domain) or LNURL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety baseline is covered. The description adds substantive behavior beyond that: it explicitly says it never requests an invoice or pays, and enumerates the fields returned even though no output schema exists. It does not cover failure modes for unreachable domains or invalid inputs beyond the 'valid' flag.

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?

Two tight sentences with no filler; the resolution behavior and return fields come first, and the 'never pays' reassurance follows immediately. Every clause carries actionable information.

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?

With no output schema, the description takes on the burden of describing return values and does so concretely (validity, min/max sats, comment length, Nostr zap support, description). Single fully-documented parameter and covered annotations mean little is missing, though network-failure or unsupported-address behavior is unstated.

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 coverage is 100% for the single 'address' parameter, so the baseline is 3. The description does add meaning by naming accepted formats (user@domain, bech32 LNURL) and extending acceptance to BOLT11 invoices, which the schema parameter text does not mention, but this is a modest incremental contribution.

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?

States a specific verb and resource: resolve a Lightning address or bech32 LNURL to its LNURL-pay endpoint and report validity and limits. The resource is distinct from siblings like btc_price or mempool_fees, though the description never explicitly contrasts with crypto_address_validate, which could plausibly be confused with this.

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 strongly implied by 'Resolve a Lightning address ... and return whether it is valid' and by the note that it also recognizes BOLT11 invoices, which hints at input acceptance. However, there is no explicit statement of when to prefer this over crypto_address_validate or btc_price, and no when-not-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources