Skip to main content
Glama

www.livero.cz catalog

Get Order Status

get_order_status
Read-only

Status of the customer's order in this shop: order status, items, shipping (tracking, pickup point) and payment. Requires the order number and the e-mail the order was placed with, both provided by the customer; never guess them or retry with variations. Repeated failed attempts block verification for a while, also on the shop website; then stop and point the customer to continue_url.

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": {
      "order_code": "<order_code>",
      "email": "<email>"
    },
    "name": "get_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesE-mail address the order was placed with.
order_codeYesOrder number exactly as the customer gives it.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The annotations only say this is a safe, non-open-world read, but the description discloses a non-obvious side effect: repeated failed attempts temporarily block verification, including on the shop website. It also supplies the recovery path (continue_url) and the trust requirement for credentials, which an agent could not infer from the annotation set.

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?

Purpose is front-loaded in the first clause, followed by prerequisites and then failure handling in a logical order. Nearly every clause carries operational information, though the opening 'order status ... order status' phrasing is mildly redundant and the sentence is dense enough to benefit from splitting.

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

Completeness5/5

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

For a two-parameter lookup with an output schema and existing annotations, the description covers everything an agent needs: what it returns, what credentials are required, how not to retry, and where to send the customer when verification is blocked. Return-value detail is correctly left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description adds real meaning on top: both values must come from the customer, must be exact ('as the customer gives it'), and must not be guessed or varied on retry. That is a behavioral constraint on the parameters that the schema's type/length constraints do not express.

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?

The description names the resource (the customer's order in this shop) and enumerates exactly what is returned: status, items, shipping with tracking/pickup point, and payment. That scope clearly separates it from catalog/product siblings like get_product or search_catalog. It stops short of an explicit verb-and-scope contrast with a specific alternative, so it lands at 4 rather than 5.

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 gives concrete preconditions (order number plus the e-mail used at purchase, both supplied by the customer) and explicit negative guidance: never guess, never retry with variations, and stop and redirect to continue_url on repeated failure. The only gap is that it never names a sibling alternative for cases where the lookup target is not an order.

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