Skip to main content
Glama

getecoback-climate-weather

geraet_bundle_aufpreis_gebrauchswert

Read-only

Aufpreis eines Pakets nur gegen die Einzelpreise tatsächlich benötigter, bestätigter Extra-Teile rechnen — Value only wanted and confirmed extras when comparing a bundle premium.

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": {
      "basis_eur": "<basis_eur>",
      "paket_eur": "<paket_eur>",
      "extras_separat_eur": "<extras_separat_eur>",
      "teile_geprueft": "<teile_geprueft>"
    },
    "name": "geraet_bundle_aufpreis_gebrauchswert"
  }
}

Input Schema

NameRequiredDescriptionDefault
basis_eurYesGesamtpreis des Basispakets.
paket_eurYesGesamtpreis des größeren Pakets für dieselbe Grundvariante.
teile_geprueftYesSind benötigte Extras und deren Kompatibilität für dasselbe Gerät belegt?
extras_separat_eurYesGesamte Einzelkosten bestätigter Extras, die du tatsächlich kaufen würdest.

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 and the bar for the description is lower. The description does add computational policy – only confirmed, actually-needed extras count – which is useful behavior beyond the annotations. It says nothing about what the tool returns (a euro delta, a verdict, a ratio), which is the main behavioral gap.

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?

The operative rule is front-loaded in a single compact sentence, and the English rendering aids cross-lingual callers. The bilingual duplication is mild redundancy but each version is short, so little is wasted.

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?

For a four-parameter financial comparison with no output schema, the definition should indicate what the computation yields and how the inputs relate (premium vs. extra costs). It covers the input policy well enough to call the tool but leaves the result shape entirely unspecified.

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% and every property already carries a German description, so the schema does the heavy lifting. The description reinforces the semantics of 'extras_separat_eur' and 'teile_geprueft' ('tatsächlich benötigt, bestätigt') but adds no format, unit, or edge-case detail beyond the schema. Baseline 3 applies.

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 names a specific computation: comparing a bundle premium ('Aufpreis eines Pakets') against the individual prices of extras, restricted to wanted and confirmed parts. That is a concrete verb+resource rather than a restatement of the name. It does not, however, contrast itself with any sibling such as the other 'gegen_aufpreis' tools, so differentiation is left to the caller.

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 clause 'nur gegen die Einzelpreise tatsächlich benötigter, bestätigter Extra-Teile' implies the condition under which the comparison is valid, which is real usage guidance. But there is no explicit when-to-use/when-not statement and no named alternative for a plain (unfiltered) bundle premium comparison.

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