Skip to main content
Glama
Sign In

FrankKi

by app.frankki
OverviewDiscussionsAdmin

Einlieferungsbeleg abrufen

order_einlieferungsbeleg
Read-only

Liefert den Einlieferungsbeleg (Einlieferungsnachweis) zu einem versendeten Auftrag, sobald der Brief eingeliefert ist und der Versanddienstleister einen Beleg ausstellt: eine 7 Tage gültige Download-URL für den Beleg (eine PDF, wenn der Versanddienstleister eine ausstellt, sonst ein JSON-Nachweis aus seinen Statusdaten; belegFormat nennt das Format, ein neuer Aufruf liefert einen frischen Link), den Poststempel, den Versanddienstleister sowie den geprüften Nachweis aus dem GoBD-Archiv. Der Beleg zeigt die Einlieferung bei der Post. Sendungsnummer und Zustellstatus eines Einschreibens liefert order_status. EN: Returns the proof of posting (Einlieferungsbeleg) for a sent order, once the letter is handed in and the mail provider issues one: a download URL for the receipt valid for 7 days (a PDF where the mail provider issues one, otherwise a JSON record built from its status data; belegFormat names the format, and a new call returns a fresh link), the postmark, the mail provider and the verified record from the GoBD archive. The receipt shows the hand-in at the post. The tracking number and delivery status of registered mail come from order_status.

Input Schema

NameRequiredDescriptionDefault
orderIdYes
reasoningNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly and non-destructive behavior, and the description adds substantial context beyond them: 7-day URL validity, fresh link on each call, belegFormat naming PDF vs JSON, and inclusion of verified GoBD archive data. It does not cover authorization or failure/error behavior, but the behavioral profile is otherwise rich.

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 core content is front-loaded and each sentence carries information, but the full German and English duplication roughly doubles length without adding distinct semantics. Appropriate for a bilingual audience, yet inefficient overall.

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?

Given no output schema, the description explains return contents well: URL validity, format naming, postmark, provider, and GoBD record. The main remaining gap is the undocumented 'reasoning' parameter, which is not addressed anywhere.

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 coverage is 0%, so the description must compensate. It only implies that an order is addressed ('zu einem versendeten Auftrag'), which loosely maps to orderId, but never explicitly explains orderId's role or format, and the 'reasoning' parameter is entirely unmentioned.

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: returns the Einlieferungsbeleg/proof of posting for a sent order. It explicitly names what is returned (download URL, postmark, mail provider, GoBD archive record) and distinguishes itself from order_status for tracking/delivery status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition: only once the letter is handed in and the mail provider issues a receipt. It also names the alternative order_status for tracking number and delivery status, so an agent knows when not to use this tool.

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

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

Resources