Skip to main content
Glama

getecoback-climate-weather

klima_kaufzeitpunkt_eigenbedarf

Read-only

Zeitfenster für einen Klimagerätekauf aus Bedarf und bestätigter Lieferzeit planen — Decide whether the current quote fits an actual deadline and budget.

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": {
      "tage_bis_bedarf": "<tage_bis_bedarf>",
      "lieferdauer_tage": "<lieferdauer_tage>",
      "einrichten_tage": "<einrichten_tage>",
      "preis_eur": "<preis_eur>",
      "deckel_eur": "<deckel_eur>",
      "frist_belegt": "<frist_belegt>"
    },
    "name": "klima_kaufzeitpunkt_eigenbedarf"
  }
}

Input Schema

NameRequiredDescriptionDefault
preis_eurYesAktueller Gesamtpreis dieses Angebots in Euro.
deckel_eurYesEigenes maximales Ausgabebudget in Euro.
frist_belegtYesLieferdauer stammt vom gewählten Verkäufer und gilt für diese Variante?
einrichten_tageYesZusätzliche Zeit bis zur Nutzung inklusive Aufstellung.
tage_bis_bedarfYesTage bis zum geplanten Einsatz.
lieferdauer_tageYesBeim konkreten Angebot bestätigte Dauer bis zur Lieferung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 the agent knows this is a closed-world, non-mutating calculation. The description adds that the tool renders a fit/no-fit judgement against both deadline and budget, which is useful. It does not disclose what happens when frist_belegt is false — whether the result is refused, degraded, or flagged — which is the main behavioral unknown for a gate parameter.

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?

It is a single sentence with the primary action front-loaded and the decision criterion appended. The German and English halves partly duplicate each other, which is mild redundancy but also serves bilingual robustness, so no more than a small deduction.

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?

Six required parameters at full schema coverage means the inputs are well specified, and the read-only annotations keep the safety profile clear. What is missing is the return shape: no output schema exists and the description never says whether the agent receives a verdict, a computed date window, or both. For a decision tool whose whole value is its conclusion, that gap is noticeable.

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% and every one of the six parameters carries a German-language description with bounds, so the schema already does the semantic work. The description merely restates the deadline/budget framing and adds no interpretation of how the parameters interact. Baseline 3 is appropriate.

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 description gives a specific verb-and-resource framing: plan a purchase time window from need plus confirmed delivery time, and decide whether the current quote fits deadline and budget. That is concrete enough to distinguish a computation/verdict tool from the surrounding check-and-compare siblings. It stops short of naming a sibling or stating the output form, so it is clear but not fully differentiated.

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?

The phrasing 'current quote' and 'confirmed delivery time' implies the tool is used once an offer with a seller-confirmed lead time exists, which is real usage context. However, there is no explicit when-to-use or when-not-to-use statement, and no pointer to alternatives such as the price-comparison sibling. Guidance is implied rather than stated.

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