FrankKi

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. Die eingebettete Karte ist Vorschau und Freigabe. Nach ihrer Anzeige reicht im Chat eine kurze Bestätigung; PDF-Link und Brieftext gehören in 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. 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. The embedded card is the preview and approval. Once it appears, a short chat confirmation is enough; PDF links and letter text belong in 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.

Input Schema

Name	Required	Description
`color`	No	Ohne Angabe wird die Farbe automatisch erkannt. EN: If omitted, colour is detected automatically.
`dryRun`	No
`reason`	No	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.
`content`	No
`express`	No
`subject`	No
`auditTag`	No
`letterId`	No	Bestehender Entwurf. Alternativ den Brief inline angeben. EN: Existing draft. Alternatively provide the letter inline.
`reasoning`	No
`presetName`	No
`templateId`	No
`scheduledAt`	No
`signatureId`	No
`approvalMode`	No
`deliveryType`	No	Standard standard. EN: Defaults to standard.
`maxCostEuros`	No	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.
`recipientZip`	No
`clientOrderId`	No	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.
`recipientCity`	No
`recipientName`	No
`mandantennummer`	No
`recipientStreet`	No
`senderAddressId`	No
`senderProfileId`	No
`includeSignature`	No
`recipientCompany`	No
`recipientCountry`	No	ISO-3166-alpha-2, Standard DE. EN: ISO 3166-1 alpha-2, defaults to DE.
`requesterContext`	No	Zusatzkontext zur einreichenden Person oder zum Anlass. EN: Additional context about the submitter or the occasion.
`recipientHouseNumber`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 16, 2026

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."

Changed1 schema field changedSep 13, 2026

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"
+]

First observedAug 8, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds substantial behavioral context beyond them: it validates mandatory details, creates a final PDF, calculates price, reserves cost, inserts into the approval queue, and explains that dryRun leaves balance and queue untouched. It also clarifies card/portal behavior after submission.

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 purpose is front-loaded and the workflow is logically ordered, but the full German and English duplication doubles the length without adding new information. The description is not bloated for a complex tool, yet it could be tighter by avoiding duplicate text and grouping related parameter behavior.

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 29-parameter tool with low schema description coverage and no output schema, the description covers the workflow and side effects well but leaves significant gaps around parameter roles and return/result expectations. It is minimum viable but not fully complete for an agent to invoke confidently with all optional parameters.

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?

With 29 parameters and only 28% schema description coverage, the description must compensate but does not. It mentions high-level concepts like Pflichtangaben, Empfänger, AVV, Limits, and dryRun, but leaves most parameters (content, recipient fields, templateId, scheduledAt, etc.) unexplained. It also references approval:self_approve, which is not present in the approvalMode enum, adding ambiguity.

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 and resource ('submits a letter') and the exact workflow goal ('for human approval'), then enumerates validation, PDF creation, pricing, cost reservation, and queue insertion. This clearly distinguishes it from approval_decide, approval_list, and letter_create_draft by making it the submission step.

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?

The description gives clear context for use: submitting a letter for human approval, with conditional behavior for approval:self_approve and dryRun. It does not explicitly name alternatives like approval_decide or letter_create_draft, so exclusions are absent, but the intended invocation context is clear.

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

All FrankKi 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.

Zur Freigabe einreichen

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources