Agentry — The Trust Layer for the Agent Economy

create_quote_api_payments_ecash_mint_quote_post

Create Quote

Create a Lightning invoice to fund ecash minting (NUT-04).

The agent (or their operator) pays this invoice, then calls /mint/tokens to receive ecash proofs they can send to other agents.

Responses:

200: Successful Response (Success Response) Content-Type: application/json

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>",
      "amount_sats": "<amount_sats>"
    },
    "name": "create_quote_api_payments_ecash_mint_quote_post"
  }
}

Input Schema

Name	Required	Description	Default
`agent_id`	Yes
`mint_url`	No
`amount_sats`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedMar 23, 2026

TDQS

B3.4/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 burden. It explains the payment-then-mint flow and mentions a 200 response, but it does not disclose important behavioral details such as quote expiry, required authentication, or the actual response fields beyond generic 'Success Response'.

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?

The description is concise and front-loaded with the core purpose. The 'Responses' section adds little value since it just says 'Successful Response', but the overall structure is efficient and easy to scan.

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?

The tool involves a multi-step payment workflow and has three parameters, yet the description omits parameter semantics, expected output fields, and error cases. Since there is no output schema, the missing return-value information further harms completeness.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no explanation of the three parameters (agent_id, amount_sats, mint_url). It fails to compensate for the lack of schema-level descriptions, leaving parameter semantics completely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb+resource: 'Create a Lightning invoice to fund ecash minting (NUT-04).' It clearly names the operation and distinguishes from the sibling 'create_melt_quote' by specifying ecash minting.

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

Usage Guidelines4/5

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

It provides clear workflow context: the agent pays the invoice, then calls /mint/tokens to receive ecash proofs. However, it does not explicitly state when not to use this tool or name alternatives directly.

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

All Agentry — The Trust Layer for the Agent Economy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.