Skip to main content
Glama

Zur Freigabe einreichen

approval_submit

Reicht einen Brief zur menschlichen Freigabe ein: prüft Pflichtangaben, Empfänger, AVV und Limits, erstellt die finale PDF, berechnet den Preis, reserviert die Kosten und legt eine Freigabe in der Warteschlange an. Sie wartet auf die Entscheidung eines Menschen, auch mit Autopilot. Die eingebettete Karte ist Vorschau und Freigabe. PDF-Link und Brieftext stehen zusätzlich im Ergebnis, für reine Textansichten. Mit approval:self_approve zeigt die Karte Freigeben und Ablehnen. In allen anderen Fällen führt sie ins angemeldete Portal. Mit dryRun bleiben Guthaben und Warteschlange unberührt, und die Antwort enthält die Liste checks (jede Prüfung mit passed, failed oder skipped). EN: Submits a letter for human approval: checks mandatory details, recipient, data processing agreement and limits, creates the final PDF, calculates the price, reserves the cost and adds an approval to the queue. It waits for a person's decision, also with autopilot. The embedded card is the preview and approval. The PDF link and letter text are also in the result, for text-only views. With approval:self_approve, the card shows Approve and Reject. In every other case it opens the signed-in portal. With dryRun, the balance and queue remain untouched, and the answer contains the checks list (each gate with passed, failed or skipped).

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": "approval_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoOhne Angabe wird die Farbe automatisch erkannt. EN: If omitted, colour is detected automatically.
dryRunNo
reasonNoKurzer Grund für die Freigabe, den die prüfende Person auf der Karte liest. EN: Short reason for the approval, shown to the reviewer on the card.
contentNo
expressNo
subjectNo
auditTagNo
letterIdNoBestehender Entwurf. Alternativ kommt der Brief inline. EN: Existing draft. The letter can come inline instead.
reasoningNo
presetNameNo
templateIdNo
scheduledAtNo
signatureIdNo
approvalModeNo
deliveryTypeNoStandard standard. EN: Defaults to standard.
maxCostEurosNoMaximalbetrag in Euro. Liegt der Preis darüber, wird abgebrochen. EN: Maximum amount in euros. If the price is above it, the call is aborted.
recipientZipNo
clientOrderIdNoIdempotenzschlüssel. Ein erneuter Aufruf mit demselben Wert liefert dieselbe Freigabe, statt ein zweites Mal einzureichen. Der Präfix 'approval:' ist reserviert. EN: Idempotency key. A repeat call with the same value returns the same approval instead of submitting a second time. The 'approval:' prefix is reserved.
recipientCityNo
recipientNameNo
mandantennummerNo
recipientStreetNo
senderAddressIdNo
senderProfileIdNo
includeSignatureNo
recipientCompanyNo
recipientCountryNoISO-3166-alpha-2, Standard DE. EN: ISO 3166-1 alpha-2, defaults to DE.
requesterContextNoZusatzkontext zur einreichenden Person oder zum Anlass. EN: Additional context about the submitter or the occasion.
recipientAddressIdNoEine gespeicherte Adresse aus dem Adressbuch (address_list) als Empfänger, an Stelle der Felder recipientName bis recipientCountry. EN: A saved address from the address book (address_list) as the recipient, in place of the fields recipientName to recipientCountry.
recipientHouseNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / recipientAddressId
      Added value: +{
      +  "description": "Eine gespeicherte Adresse aus dem Adressbuch (address_list) als Empfänger, an Stelle der Felder recipientName bis recipientCountry. EN: A saved address from the address book (address_list) as the recipient, in place of the fields recipientName to recipientCountry.",
      +  "format": "uuid",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / letterId / description
      Previous value: -"Bestehender Entwurf. Alternativ den Brief inline angeben. EN: Existing draft. Alternatively provide the letter inline."New value: +"Bestehender Entwurf. Alternativ kommt der Brief inline. EN: Existing draft. The letter can come inline instead."
  3. Changed3 schema fields changed
    • changedInput schema / properties / clientOrderId / description
      Previous value: -"Idempotenzschluessel. Ein erneuter Aufruf mit demselben Wert liefert dieselbe Freigabe, statt ein zweites Mal einzureichen. Der Praefix 'approval:' ist reserviert. EN: Idempotency key. A repeat call with the same value returns the same approval instead of submitting a second time. The 'approval:' prefix is reserved."New value: +"Idempotenzschlüssel. Ein erneuter Aufruf mit demselben Wert liefert dieselbe Freigabe, statt ein zweites Mal einzureichen. Der Präfix 'approval:' ist reserviert. EN: Idempotency key. A repeat call with the same value returns the same approval instead of submitting a second time. The 'approval:' prefix is reserved."
    • changedInput schema / properties / maxCostEuros / description
      Previous value: -"Maximalbetrag in Euro. Liegt der Preis darueber, wird abgebrochen. EN: Maximum amount in euros. If the price is above it, the call is aborted."New value: +"Maximalbetrag in Euro. Liegt der Preis darüber, wird abgebrochen. EN: Maximum amount in euros. If the price is above it, the call is aborted."
    • changedInput schema / properties / reason / description
      Previous value: -"Kurzer Grund fuer die Freigabe, den die pruefende Person auf der Karte liest. EN: Short reason for the approval, shown to the reviewer on the card."New value: +"Kurzer Grund für die Freigabe, den die prüfende Person auf der Karte liest. EN: Short reason for the approval, shown to the reviewer on the card."
  4. Changed1 schema field changed
    • changedInput schema / properties / deliveryType / enum
      Previous value: -[
      -  "standard",
      -  "einschreiben_einwurf",
      -  "einschreiben_uebergabe"
      -]New value: +[
      +  "standard",
      +  "einschreiben_einwurf",
      +  "einschreiben_uebergabe",
      +  "ch_b_post",
      +  "ch_a_post",
      +  "ch_einschreiben",
      +  "at_eco",
      +  "at_prio",
      +  "intl_standard",
      +  "intl_priority",
      +  "intl_express",
      +  "intl_tracked",
      +  "intl_registered"
      +]
  5. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=false; the description adds real substance beyond that – it reserves cost, blocks on a human decision even under autopilot, and dryRun leaves balance and queue untouched and returns a checks list. The reference to 'approval:self_approve' does not correspond to any parameter in the schema (approvalMode is auto/draft/review), which muddies an otherwise strong disclosure.

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 pipeline is front-loaded, which is good, but the entire text is duplicated verbatim in German and English, roughly doubling the token cost with zero added information. Within each language block the sentences are dense but each carries a distinct behavioral fact.

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?

For a 30-parameter, zero-required, no-output-schema tool, the definition covers the submission lifecycle and the shape of the dry-run response (checks list, PDF link, letter text), but leaves the core content inputs (content vs letterId vs templateId vs presetName, approvalMode semantics) unexplained. An agent can act on it roughly but not confidently about which input combination to supply.

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 30% for 30 parameters, so the description must compensate but does not: it explains only dryRun's effect and mentions an 'approval:self_approve' mode that has no matching parameter. The recipient fields, subject, content, templateId, presetName, signatureId, express, includeSignature, auditTag and others get no semantic help from the description.

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 first sentence gives a precise verb and resource ('Reicht einen Brief zur menschlichen Freigabe ein') and enumerates the whole pipeline: validation of mandatory fields, recipient, AVV and limits, PDF creation, price calculation, cost reservation, and queue entry. It implicitly separates itself from approval_decide ('it waits for a person's decision') and from a send tool, but no sibling is named explicitly, so it stops short of a 5.

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 context is implied rather than stated: the agent can infer that dryRun is for a safe preview run and that the card handles approval. There is no explicit 'use this instead of letter_schedule / order_send / approval_decide' guidance, and no prerequisites (wallet balance, signed-in portal, existing letterId vs inline content) are spelled out as conditions for choosing this tool.

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.