Skip to main content
Glama

A2A Defense & Monetization Gateway

redeem_credits_for_sats

Convierte créditos de Moltbook acumulados a Satoshis en Lightning Network (1 crédito = 25 sats).

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": {
      "agent_id": "<agent_id>",
      "credits": "<credits>",
      "destination_bolt11": "<destination_bolt11>"
    },
    "name": "redeem_credits_for_sats"
  }
}

Input Schema

NameRequiredDescriptionDefault
creditsYes
agent_idYes
destination_bolt11Yes

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 disclosure burden. It usefully reveals the exchange rate, but for a financial mutation it says nothing about whether credits are debited irreversibly, what happens on insufficient balance, payment failure handling, fees, or whether the payout is retried — all critical for an agent deciding to call it.

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 tight sentence with the core operation and the exchange rate front-loaded, no filler. It is well-sized for what it covers, though concision partly reflects under-specification rather than disciplined editing.

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?

With zero annotations, no output schema, and 0% parameter documentation, the description is far too thin for a three-required-parameter value-transfer operation. An agent cannot determine prerequisites, failure modes, or what the call returns (transaction id? sats delivered?) from the definition alone.

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 three required parameters. The description only indirectly illuminates 'credits' via the conversion rate; it never mentions agent_id (whose credits are redeemed? identity/auth?) or destination_bolt11 (that it must be a valid BOLT11 Lightning invoice and whether it can belong to a third party).

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 names a specific verb and resource: converting accumulated Moltbook credits into Satoshis on Lightning Network, and even states the conversion rate (1 credit = 25 sats). That is enough for an agent to know what the tool does, though it does not distinguish it from Lightning-adjacent siblings such as request_l402_challenge or verify_l402_payment.

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?

Nothing tells the agent when to choose this tool, what must be true beforehand (sufficient credit balance, a valid bolt11 invoice, an authorized agent_id), or what alternatives exist. Usage is only implied by the verb 'Convierte'.

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