Skip to main content
Glama

Auftragsstatus abrufen

order_status
Read-only

Liefert den Stand eines Briefs: Status, deutsche Sendungsverfolgung, Sendungsnummer (bei Einschreiben), voraussichtliche Zustellung und ob er sich noch stornieren lässt. Der Aufruf nimmt genau eine Kennung: orderId, approvalId (aus order_send, solange orderId null ist) oder letterId. Vor dem Versand kommt status queued_autopilot mit dispatchAt, humanSummary (de, en) und cancelWith. Bei awaiting_partner_fix wartet der Brief auf order_fix_resubmit, bei failed nennt failure den Grund und nextStep den Weg zurück. Solange cancellable true ist, stoppt order_cancel den Versand. EN: Returns where a letter stands: status, German tracking history, tracking number (registered mail), estimated delivery and whether it can still be cancelled. The call takes exactly one id: orderId, approvalId (from order_send while orderId is null) or letterId. Before dispatch the status is queued_autopilot with dispatchAt, humanSummary (de, en) and cancelWith. On awaiting_partner_fix the letter waits for order_fix_resubmit; on failed, failure gives the reason and nextStep the way back. While cancellable is true, order_cancel stops the send.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdNo
letterIdNo
reasoningNo
approvalIdNoAus order_send, solange orderId null ist. EN: From order_send while orderId is null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / approvalId
      Added value: +{
      +  "description": "Aus order_send, solange orderId null ist. EN: From order_send while orderId is null.",
      +  "format": "uuid",
      +  "type": "string"
      +}
    • addedInput schema / properties / letterId
      Added value: +{
      +  "format": "uuid",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "orderId"
      -]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare a safe read, and the description goes well beyond them: it discloses the possible status values, the pre-dispatch queued_autopilot state with dispatchAt/humanSummary/cancelWith, the failure payload (failure + nextStep), and the external side effect on order_cancel. That is exactly the state-machine context an agent needs and which no annotation supplies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The German text is dense and front-loaded with return fields, but the full EN block duplicates it verbatim, roughly doubling length without adding information for most readers. The i18n motive is understandable, yet it is real redundancy against a conciseness bar.

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?

There is no output schema and low parameter coverage, so the description must carry the burden alone, and it largely does: return fields, status values and recovery paths are all named. It stops short of documenting the `reasoning` parameter and of clarifying a lookup-by-letterId vs orderId precedence.

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?

With only 25% schema coverage, the description has to compensate, and it does for three of four ids: orderId, letterId and approvalId's provenance are spelled out. The `reasoning` parameter is never mentioned, and the ids' non-obvious source for orderId/letterId is left implicit, so it's strong but not complete.

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 first sentence names a specific verb and resource ("Liefert den Stand eines Briefs") and immediately enumerates the concrete outputs: status, tracking history, tracking number, ETA, cancellability. This is distinguishable from letter_get or order_einlieferungsbeleg without opening any schema.

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 explicitly routes the caller through the state machine: awaiting_partner_fix goes to order_fix_resubmit, cancellable true permits order_cancel, and approvalId comes from order_send while orderId is null. It never states when to use this instead of the sibling letter_get, so the boundary with the closest read-sibling remains implicit.

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.