Skip to main content
Glama

AI Fusion One

Get receipt

get_receipt
Read-onlyIdempotent

Read a transaction receipt (payment status, settlement tx, request and result summary) using the transaction id and the one-time receipt token returned by a paid call. Free.

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": {
      "id": "<id>",
      "token": "<token>"
    },
    "name": "get_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYestransaction_id from the paid call's receipt.
tokenYesReceipt token (shown only once, in the paid call's receipt).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new context: the token is one-time and originates from the paid call's receipt, and the call itself is "Free" — a billing fact no annotation conveys, which matters because the preceding call was paid.

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, front-loaded with verb and resource, followed by the return contents, the required inputs, and the cost note in that order. Zero filler; even the trailing "Free." carries decision-relevant information.

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

Completeness4/5

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

With no output schema, the description usefully names the returned fields, and with a trivial two-parameter schema the input side is fully covered. What is missing is behavioral edge information — what happens if the one-time token was already used or has expired — which would be the last piece an agent needs.

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 coverage is 100%, and both parameters already carry descriptions plus regex patterns, so the schema does the heavy lifting. The description only restates the parameter roles without adding format, sourcing detail beyond "returned by a paid call," matching the baseline 3.

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?

"Read a transaction receipt" states a specific verb and resource, and the parenthetical enumerates exactly what the receipt contains (payment status, settlement tx, request/result summary). No sibling in the listed catalog touches transaction receipts, so the tool is unambiguously identifiable.

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 establishes the entry condition clearly: it is used with the transaction id and the one-time receipt token returned by a paid call, so an agent knows this is the follow-up step after a paid invocation. It does not state exclusions or failure cases (invalid/expired/already-consumed token), which keeps it from a 5.

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