Skip to main content
Glama

A2A Defense & Monetization Gateway

request_l402_challenge

Genera un desafío HTTP 402 con Macaroon criptográfico y factura Lightning Bolt11 para acceso pay-per-call.

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": {
      "service": "<service>",
      "amount_sats": "<amount_sats>",
      "client_id": "<client_id>"
    },
    "name": "request_l402_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYes
client_idYes
amount_satsYes
ttl_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses what artifacts are produced (macaroon + Bolt11 invoice) but says nothing about whether the challenge persists server-side, whether it is single-use, how ttl_seconds expiry is enforced, or what permissions/secrets are required to mint a macaroon — significant gaps for a security-credential-issuing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the key artifacts are named early. It is efficient, though its brevity is part of why other dimensions are underspecified.

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

Completeness2/5

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

For a four-parameter, zero-schema-coverage, no-annotation tool that issues cryptographic credentials, the definition is thin: no parameter meaning, no call preconditions, no indication of the challenge's return shape (macaroon string, invoice, expiry) and no hint of the follow-up verification step.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description must compensate and largely does not. It hints that amount relates to the Lightning invoice and that access is pay-per-call, but leaves 'service', 'client_id', and 'ttl_seconds' (including its default of 1800 and what expires) entirely unexplained.

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 gives a specific verb ('Genera') and concrete resource ('desafío HTTP 402 con Macaroon criptográfico y factura Lightning Bolt11'), so an agent knows this mints a payment challenge rather than verifying one. It does not explicitly name or distinguish itself from siblings like verify_l402_payment, but the purpose is far from tautological.

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

Usage Guidelines2/5

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

It states the outcome ('acceso pay-per-call') but never says when to call it versus verify_l402_payment or redeem_credits_for_sats, nor what preconditions exist (existing client registration, pricing lookup). Usage must be inferred from the tool name alone.

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