Skip to main content
Glama

getecoback-climate-weather

geraet_reparatur_ausfallkosten

Read-only

Einen Reparaturkostenvoranschlag um tatsächlich nötige Übergangsnutzung während des Ausfalls ergänzen — Add necessary downtime costs to a household repair quote.

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": {
      "reparatur_eur": "<reparatur_eur>",
      "ausfall_tage": "<ausfall_tage>",
      "freie_tage": "<freie_tage>",
      "ersatz_pro_tag_eur": "<ersatz_pro_tag_eur>",
      "ersatzbudget_eur": "<ersatzbudget_eur>"
    },
    "name": "geraet_reparatur_ausfallkosten"
  }
}

Input Schema

NameRequiredDescriptionDefault
freie_tageYesDavon Tage, die ohne zusätzliche Zahlung überbrückt werden können.
ausfall_tageYesIm Szenario erwartete Ausfallzeit.
reparatur_eurYesVollständiger Reparaturvoranschlag.
ersatzbudget_eurYesEigenes Budget für Reparatur plus Überbrückung.
ersatz_pro_tag_eurYesEigene Übergangskosten pro verbleibendem Tag.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 safety profile is clear. The description adds that it computes 'tatsächlich nötige' (actually necessary) interim costs, but it does not describe the return value, assumptions, or any calculation caveats beyond what is implied by the parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence in two languages. Every clause earns its place by stating the action and the domain, with no redundant or filler wording.

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?

For a simple five-parameter calculation tool with full schema descriptions and safety annotations, the description is mostly complete. It could be improved by clarifying the return value (e.g., whether it returns total added costs or a combined budget), but the essential purpose is covered.

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 five numeric parameters are fully documented in the input schema. The description adds no parameter-level detail or interpretation beyond what the schema already provides, which is the baseline for high-coverage schemas.

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 states a specific action ('ergänzen / add') and resource ('Übergangsnutzung / downtime costs') in the context of a household repair quote. It clearly signals a cost-calculation tool, though it does not explicitly contrast itself with sibling tools like geraet_reparaturpreis_grenze or geraet_testzitat_einordnen.

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?

Usage is implied by the action: use this when you have a repair quote and need to account for downtime costs. However, there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives, leaving the agent to infer the context.

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