Skip to main content
Glama

l402_request

Requests an L402-protected URL, pays the returned Lightning invoice via LNbits, then retries with authorization to return the unlocked response.

Instructions

Run the full L402 flow: request a URL, detect the 402 challenge, pay the invoice via LNbits, retry with Authorization, and return the unlocked response.

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": {
      "url": "<url>"
    },
    "name": "l402_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe L402-protected URL to request
bodyNoOptional request body for non-GET requests
methodNoHTTP method to use (default: GET)GET
headersNoOptional request headers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does reveal the most important behavior: it pays an invoice via LNbits, meaning real funds are spent and the operation is not a passive read. It stops short of stating payment limits, irreversibility, whether payment happens automatically without confirmation, or what happens on payment failure, which are exactly the facts an agent needs before invoking a spending 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?

A single sentence that front-loads the overall purpose and then walks the steps in execution order. No filler, no repetition of the tool name, and the sequence itself conveys the control flow.

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

Completeness3/5

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

For a four-parameter tool with a nested headers object and no output schema, the description covers inputs implicitly and describes the return only as 'the unlocked response.' Given that this tool spends money and has no annotations or output schema, the absence of any detail on payment magnitude, failure modes, or response shape leaves a meaningful gap.

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 description coverage is 100%, so url, method, headers, and body are already documented in the schema, and the description adds no parameter-level meaning. Baseline 3 is appropriate since the schema does the work.

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?

Names a specific action (run the full L402 flow) and enumerates the concrete steps: request, detect 402, pay via LNbits, retry with Authorization, return the response. That is far more precise than a bare name restatement and implicitly distinguishes it from lighter siblings like l402_check or l402_inspect, though it never names those alternatives.

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?

The phrase 'full L402 flow' implies this is the end-to-end option versus partial tools such as l402_check, but no explicit when-to-use or when-not guidance is given. An agent must infer from sibling names that this is the heavy, paying path rather than a pre-flight check.

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