Skip to main content
Glama
Sign In

Agentry — The Trust Layer for the Agent Economy

by io.github.cthulhutoo
OverviewDiscussionsAdmin

receive_ecash_api_payments_ecash_receive_post

Receive Ecash

Receive/redeem a Cashu ecash token.

The agent swaps the received proofs for new ones at the mint, ensuring the sender can't double-spend. This is the standard Cashu receive flow (NUT-03 swap).

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>",
      "token": "<token>"
    },
    "name": "receive_ecash_api_payments_ecash_receive_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
agent_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the key behavioral trait of swapping proofs at the mint to prevent double-spending, which is valuable. However, it does not mention side effects like token consumption, crediting to the agent, or idempotency, leaving gaps for a mutation operation.

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 short and front-loaded with the purpose, followed by a brief behavioral explanation and a minimal response section. It's efficiently written with no fluff, though the response section could be slightly more informative without harming conciseness.

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 simple two-parameter tool with no output schema and no annotations, the description provides the core flow but omits critical details like the exact response body, error cases, and what agent_id represents. It's not fully complete but is more informative than a bare one-liner, earning a middle score.

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%, so the description must compensate. It clarifies that 'token' is a Cashu ecash token, but provides no meaning for 'agent_id', which is a required parameter. This leaves the agent guessing about the role of agent_id, making the description insufficient for parameter understanding.

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 specific verbs 'Receive/redeem' and names the resource 'Cashu ecash token', making the tool's purpose immediately clear. It also distinguishes from siblings like 'send_ecash' by describing the receive flow and even cites the standard NUT-03 swap.

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?

The description implies the usage context: it is for receiving/redeeming ecash tokens, as opposed to sending or verifying. While it doesn't explicitly name alternatives or state when not to use the tool, the context is clear enough that an agent would know this is the counterpart to send operations.

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 toolsInspect
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.

Resources