Skip to main content
Glama

getecoback-raumklima

reparaturangebot_diagnoseabrechnung_zwei_ausgaenge

Read-only

Ein Reparaturangebot mit unterschiedlich abgerechneter Diagnose bei Ausführung und bei Verzicht auseinanderrechnen — Compare explicitly quoted costs for proceeding versus stopping after diagnosis.

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": {
      "diagnose_euro": "<diagnose_euro>",
      "reparatur_ohne_diagnose_euro": "<reparatur_ohne_diagnose_euro>",
      "diagnose_erlass_bei_auftrag_euro": "<diagnose_erlass_bei_auftrag_euro>",
      "rueckgabe_ohne_reparatur_euro": "<rueckgabe_ohne_reparatur_euro>",
      "vertragsumfang_belegt": "<vertragsumfang_belegt>"
    },
    "name": "reparaturangebot_diagnoseabrechnung_zwei_ausgaenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
diagnose_euroYesAngebotene Diagnosegebühr in Euro.
vertragsumfang_belegtYesBeide Abläufe, Gesamtabgaben und die Zuordnung aller Beträge sind im Angebot nachvollziehbar?
reparatur_ohne_diagnose_euroYesSeparater Preis der bestätigten Reparatur, ohne Diagnose gerechnet.
rueckgabe_ohne_reparatur_euroYesZusätzlich bestätigte Rückgabekosten bei Verzicht auf Reparatur.
diagnose_erlass_bei_auftrag_euroYesBei Reparaturauftrag ausdrücklich gutgeschriebener Anteil der Diagnosegebühr.

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 safety profile is covered; the description usefully clarifies that this is a pure arithmetic comparison of explicitly quoted amounts, not an estimate. However, it does not say what happens when vertragsumfang_belegt is false (error, refusal, or a degraded result) nor how inconsistent inputs are handled — significant for a tool whose only safeguard is that boolean gate.

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, two sentences and no filler. The second sentence is largely a bilingual restatement of the first, which is defensible for cross-lingual routing but does duplicate rather than extend the content.

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?

The inputs are fully specified via the schema and the two-branch framing is clear, but with no output schema an agent still cannot tell what the comparison returns (two scenario totals, a delta, a recommendation) or what the boolean gate does on failure. For a five-parameter computation tool that is a meaningful remaining gap.

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 coverage is 100%, so every parameter is already documented in the schema; the baseline is therefore 3. The description does add grouping value by mapping the parameters onto the two branches (proceeding with credited diagnosis vs. waiving with return costs), but adds no formula, sign convention, or total computation semantics beyond that.

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?

Names a concrete operation (auseinanderrechnen / compare) on a concrete resource (a repair quote's diagnosis billing) and splits it explicitly into the two branches that matter: execution vs. waiver of repair. This is far from a restatement of the name and gives an agent a usable mental model. It stops short of differentiating from any sibling, so it does not reach 5.

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 rather than stated: the description makes clear this is for reconciling two alternative quoted outcomes, which is a real trigger condition. There is no explicit 'use this instead of X', no prerequisites (e.g. that all five quoted figures must already exist in the offer), and no exclusions, so an agent must infer the boundary itself.

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