Skip to main content
Glama

get_receipt

Retrieve a past draw receipt by ID to verify an allowed or denied quota draw and audit its hash-chained record.

Instructions

Fetch a past draw receipt by id.

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

Input Schema

NameRequiredDescriptionDefault
receipt_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 burden. "Fetch" weakly implies a read, but the description does not disclose what happens for a nonexistent or malformed id, whether the caller must own the receipt, or whether receipts are ever purged — all material for a receipt-lookup 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?

One short sentence, front-loaded with the verb and resource, with no filler. It is efficient, though the brevity reflects under-specification rather than disciplined pruning.

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 is simple (one required integer, no output schema, no nesting), so not much is required — but with zero schema coverage and no annotations, the description should at minimum define the identifier and the not-found behavior. As written, the agent is left to guess both.

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% and the single parameter (receipt_id, integer) is undocumented. "By id" only weakly clarifies that the id is a receipt identifier, yet it never distinguishes it from a draw id or states format/range, so the coverage gap is not compensated.

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?

"Fetch a past draw receipt by id" gives a specific verb (fetch) and resource (draw receipt) plus the lookup key, so the agent knows this is a point-lookup, not a listing. It does not differentiate from the sibling "draw" tool, which plausibly also surfaces receipt data, so it stops short of a 5.

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?

There is no guidance on when to use this versus "draw" or any other sibling, no prerequisite or precondition stated, and no note on what to do when the id is unknown. The agent must infer the retrieval scenario entirely from the name.

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