Skip to main content
Glama

Order receipt

get_receipt
Read-onlyIdempotent

Itemized receipt for an order: items, subtotal, fees, discounts, credits, tax and total, plus payment status. Before intake the items are not known yet and the total is an estimate. Works with the connected account, or order code + the email used when scheduling.

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

Input Schema

NameRequiredDescriptionDefault
emailNoNot needed with a connected account.
orderCodeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful behavioral context by noting that before intake the items are unknown and the total is an estimate, and by explaining the two access modes.

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?

The description is front-loaded with the core purpose, then adds the estimate caveat and access modes in three efficient sentences. Every sentence contributes useful information without filler.

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 appropriately enumerates the receipt contents and payment status, and it covers the pre-intake estimate caveat and access modes. It could do more to explain how to obtain orderCode, but it is otherwise complete for a read-only receipt lookup.

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 50%, and orderCode has no schema description. The description clarifies that email is the email used when scheduling and that order code plus email is an alternative to a connected account, but it does not specify orderCode format or where to obtain it.

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 states exactly what the tool returns: an itemized receipt for an order with line items, subtotal, fees, discounts, credits, tax, total, and payment status. It also distinguishes the pre-intake estimate case, making it clear this is not merely an estimate or tracking call.

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

Usage Guidelines3/5

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

Usage is implied by 'receipt for an order,' but there is no explicit when-to-use/when-not guidance and no named alternatives such as get_estimate, list_my_orders, or track_order. The access-mode sentence explains authentication, not tool selection.

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