Overfit — German tenders & procurement law

Wartefrist nach § 134 GWB

vergabe_wartefrist

Read-onlyIdempotent

Earliest date a contracting authority may award the contract after informing the unsuccessful bidders (§ 134 GWB). absendung = the date the § 134 GWB bidder information is sent after the bids were evaluated (not the contract notice date); the period starts with that dispatch. Returns both interpretations of the § 134 GWB standstill: the strict end date (no weekend shift, per VK Bund) and the conservative one (shifted to next working day, per OLG Bremen) — electronic dispatch 10 days, postal 15 days (Stand 2026-07-14). Suited to the question on which date a contract may be awarded after informing unsuccessful bidders. The BGH has not resolved the weekend-shift question; the conservative date is the safer one. zuschlag_praktisch_* + praxishinweis give the first working day on which the award can practically be made (weekends and public holidays skipped; state holidays via the optional land). Tender and participation deadlines are computed by vergabe_fristen_berechnen.

Example user questions: "Wann endet die Wartefrist nach § 134 GWB?"; "Ab wann darf ich den Zuschlag erteilen?"; "Wie lange muss ich nach der Bieterinformation warten?"; "10 Tage Wartefrist — wann ist das genau?"

Input Schema

TableJSON Schema

Name	Required	Description
`land`	No	Optional federal state of the contracting authority; only used for the practical award date (state public holidays).
`absendung`	Yes	Date the § 134 GWB bidder information (Vorabinformation to unsuccessful bidders) is or was sent — not the contract notice date. ISO 2026-10-05 or German 05.10.2026.
`elektronisch`	No	Electronic or fax dispatch (10 days); false = postal (15 days). Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 6, 2026

changedInput schema / properties / absendung / description

Previous value: -"Date the bidder information was dispatched (ISO or German format)."New value: +"Date the § 134 GWB bidder information (Vorabinformation to unsuccessful bidders) is or was sent — not the contract notice date. ISO 2026-10-05 or German 05.10.2026."

addedInput schema / properties / land

Added value: +{
+  "description": "Optional federal state of the contracting authority; only used for the practical award date (state public holidays).",
+  "enum": [
+    "BW",
+    "BY",
+    "BE",
+    "BB",
+    "HB",
+    "HH",
+    "HE",
+    "MV",
+    "NI",
+    "NW",
+    "RP",
+    "SL",
+    "SN",
+    "ST",
+    "SH",
+    "TH"
+  ],
+  "examples": [
+    "BY"
+  ],
+  "type": "string"
+}

First observedOct 5, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare readOnly/idempotent/openWorld, and the description adds substantial domain behavior beyond that: exactly what date 'absendung' means, that both § 134 interpretations are returned, the 10/15-day split by dispatch mode, the legal positions (VK Bund vs OLG Bremen), and that the conservative date is safer. This is behavior an agent cannot infer from annotations.

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?

Front-loaded with the core semantics, then the legal nuances, then examples. Dense but organized. Slightly over-long — the example-question sentence is somewhat redundant given the preceding usage sentence — but every block carries information.

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

Completeness5/5

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

A no-output-schema, 3-parameter computation tool is fully covered: the meaning of each parameter, the two returned date interpretations, the legal ambiguity, which is the safer choice, and which sibling handles adjacent deadlines. Nothing an agent needs to call or interpret this is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description still adds meaning by clarifying that 'absendung' is the bidder-information dispatch date, not the contract notice date, and that 'land' only affects the practical date. That disambiguation is valuable even against a well-described schema.

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+resource: computes the earliest award date (Wartefrist) under § 134 GWB. Clearly distinguishes from sibling vergabe_fristen_berechnen, which it names as handling tender/participation deadlines instead.

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?

Explicitly names the use case ('Suited to the question on which date a contract may be awarded') and routes the sibling case (tender/participation deadlines) to vergabe_fristen_berechnen. Includes example user questions that map directly onto invocation scenarios.

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

All Overfit — German tenders & procurement law 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.

Resources

Need Help?