Café QR

Look up an order

get_order

Read-onlyIdempotent

One order in full by its order number (e.g. K7M2Q) or receipt number: items and options, totals, VAT, discount, tip, payment, refund and who took it. Guest contact details are not included.

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": {
      "orderNumber": "<orderNumber>"
    },
    "name": "get_order"
  }
}

Input Schema

Name	Required	Description	Default
`cafe`	No	Which café, by name or slug. Only needed when the person has more than one (see list_my_cafes).
`orderNumber`	Yes	The order or receipt number.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, and non-destructive behavior. The description adds valuable detail about what data is returned (items, totals, VAT, payment, refund, etc.) and explicitly notes that guest contact details are excluded, which is useful contextual information beyond the annotations.

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 two sentences, front-loaded with the core action and data scope, and contains no redundant wording. Every sentence earns its place.

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?

For a read-only lookup tool with no output schema, the description adequately explains what will be returned and excludes. It does not mention error cases (e.g., order not found) or authentication requirements, but these are minor given the annotations and simplicity of the tool.

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 description coverage is 100%, so the schema already documents both parameters (orderNumber as order or receipt number, cafe for multi-café users). The description only adds an example format (K7M2Q) and does not explain the cafe parameter, so added value beyond the schema is minimal.

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 a specific verb and resource: retrieve 'one order in full' by order or receipt number, and enumerates the returned data. It implicitly distinguishes itself from sibling tools like list_orders by emphasizing a single complete order.

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 clearly indicates the input needed (order number or receipt number, with an example) and implies use when a specific order is known. However, it does not explicitly name alternatives such as list_orders for finding an order, leaving some inference to the agent.

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

All Café QR 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.

Resources

Need Help?