Skip to main content
Glama

Adresse korrigieren und erneut senden

order_fix_resubmit
Destructive

Korrigiert die Empfängeradresse eines Briefs im Status awaiting_partner_fix und reicht ihn erneut ein. Das setzt voraus, dass die OAuth-Verbindung approval:self_approve trägt. Andernfalls liefert der Aufruf einen Link, über den der Mensch im angemeldeten Portal entscheidet. Der Preis bleibt unverändert. EN: Corrects the recipient address of a letter in awaiting_partner_fix and resubmits it. This requires that the OAuth connection carries approval:self_approve. Otherwise the call returns a link where the human decides in the signed-in portal. The price stays unchanged.

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": {
      "orderId": "<orderId>",
      "recipient": "<recipient>"
    },
    "name": "order_fix_resubmit"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYes
reasoningNo
recipientYesDie korrigierte Empfängeradresse als Einzelfelder oder als { addressId } aus dem Partner-Adressbuch. EN: The corrected recipient address as inline fields or as { addressId } from the partner address book.
clientOrderIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / recipient / description
      Previous value: -"Die korrigierte Empfaengeradresse als Einzelfelder oder als { addressId } aus dem Partner-Adressbuch. EN: The corrected recipient address as inline fields or as { addressId } from the partner address book."New value: +"Die korrigierte Empfängeradresse als Einzelfelder oder als { addressId } aus dem Partner-Adressbuch. EN: The corrected recipient address as inline fields or as { addressId } from the partner address book."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only flag destructive/openWorld; the description adds real value beyond them: the required OAuth scope, the human-in-the-loop fallback returning a link, and the guarantee that the price is unchanged. It still does not state whether resubmission re-triggers printing/postage consumption or whether the correction is reversible, which matters for a destructiveHint=true 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?

Well front-loaded: the action, then the precondition, then the fallback, then the price guarantee — each sentence carries information. The German/English duplication roughly doubles the length without adding content, which is the only structural cost.

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

Completeness3/5

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

Covers the critical operational context (precondition, auth scope, approval fallback, cost) for a mutation tool with no output schema. However, it leaves the purpose of 'reasoning' and 'clientOrderId' (idempotency?) unexplained and gives no indication of what the success response contains or how the returned approval link should be handled.

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 only 25% and the description explains no parameters at all — orderId, reasoning and clientOrderId are undocumented in both places, and the two recipient shapes are only described in the schema itself. With a low coverage ratio the description should compensate, and it does not.

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?

States a specific verb pair (correct address, resubmit) and pins the resource to letters in the 'awaiting_partner_fix' state, which cleanly separates it from order_send, order_send_batch and setup_fix_link. The state precondition makes the scope unambiguous without opening the 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?

Gives a clear when-to-use condition (letter must be in awaiting_partner_fix) and describes the fallback path when the OAuth scope approval:self_approve is absent. It does not explicitly name sibling alternatives (e.g. setup_fix_link or order_cancel) for other order states, so the routing is implied rather than enumerated.

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.