Skip to main content
Glama

getecoback-climate-weather

reparaturangebot_annahme_material_fristkonflikt

Read-only

Prüfen, ob ein belegter Annahmetermin mit der separat zugesicherten Teilebindung zeitlich zusammenpasst — Detect when reservation expires before an offer can actually be accepted.

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": {
      "angebot_bis": "<angebot_bis>",
      "teil_reserviert_bis": "<teil_reserviert_bis>",
      "annahme_fruehestens": "<annahme_fruehestens>",
      "gleicher_auftrag": "<gleicher_auftrag>"
    },
    "name": "reparaturangebot_annahme_material_fristkonflikt"
  }
}

Input Schema

NameRequiredDescriptionDefault
angebot_bisYesLetzter ausdrücklich bestätigter Annahmetag des schriftlichen Angebots. Datum YYYY-MM-DD, leer wenn unbekannt.
gleicher_auftragYesBetreffen Zusagen dasselbe konkrete Gerät, dieselbe Teileversion und denselben Anbieter?
annahme_fruehestensYesTatsächlich frühester möglicher Annahmetag. Datum YYYY-MM-DD, leer wenn unbekannt.
teil_reserviert_bisYesLetzter ausdrücklich belegter Tag der separaten Teilreservierung. Datum YYYY-MM-DD, leer wenn unbekannt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered and 'Prüfen' is consistent with them. The description adds the logical conflict condition, which is real value, but it says nothing about the outcome shape (flag/enum/report) or about what happens when input dates are 'leer wenn unbekannt' — a documented edge case the tool must handle.

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?

Two clauses, front-loaded with the verb, but the German half is a single convoluted noun-stack and the bilingual duplication partially repeats rather than sharpens the claim. Nothing is clearly disposable, yet the sentence does not land the condition cleanly on first read.

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?

All four required parameters are fully described in the schema and there is no output schema, so the description should carry the burden of explaining what a successful call yields. It identifies the check but not the result form or the unknown-date behaviour, which for a four-required-parameter diagnostic tool is a noticeable hole.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters are already documented, and this is the baseline 3. The description adds only the relational semantics — that the two date fields are compared against each other for temporal fit — without adding syntax, defaults, or guidance on the unknown-date case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb is the generic 'Prüfen' and the object ('belegter Annahmetermin' vs 'separat zugesicherte Teilebindung') is a dense domain compound. The appended English clause ('Detect when reservation expires before an offer can actually be accepted') is much more concrete and finally pins down the condition being tested, but it is not a clean restatement of the German clause, leaving the agent to reconcile two phrasings of the purpose.

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

Usage Guidelines2/5

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

There is no statement of when this check should be run, no prerequisites (e.g. that the quote and the parts reservation must concern the same job), and no named alternative among the plausible siblings. The 'gleicher_auftrag' parameter implies some precondition, but the description never says what to do when it is false.

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.

Resources