Skip to main content
Glama

getecoback-climate-weather

angebote_gesamtpreis_vergleichen

Read-only

Zwei gleich ausgestattete Angebote inklusive notwendiger Zusatzkosten vergleichen — Compare delivered purchase totals for matched quotes.

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": {
      "a_eur": "<a_eur>",
      "b_eur": "<b_eur>",
      "a_zusatz_eur": "<a_zusatz_eur>",
      "b_zusatz_eur": "<b_zusatz_eur>",
      "gleich": "<gleich>",
      "vollstaendig": "<vollstaendig>"
    },
    "name": "angebote_gesamtpreis_vergleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_eurYesGerätepreis A inklusive ausgewiesener Steuern in Euro.
b_eurYesGerätepreis B inklusive ausgewiesener Steuern in Euro.
gleichYesSind konkrete Variante, Umfang und Zustand gleich?
a_zusatz_eurYesVersand und notwendige Zubehör-/Servicekosten in A.
b_zusatz_eurYesVersand und notwendige Zubehör-/Servicekosten in B.
vollstaendigYesSind alle für beide Angebote notwendigen Zusatzkosten bekannt?

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 it is clear this is a pure, offline calculation. The description adds that mandatory ancillary costs must be included and that offers must be matched, which is useful behavioral context, but it says nothing about the result (no output schema exists) or how the 'gleich'/'vollstaendig' flags affect the computation.

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?

Two short clauses, one German and one English gloss, with the key scope constraint ('gleich ausgestattete') front-loaded. No filler, though the bilingual duplication is slightly redundant.

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 six-required-parameter, read-only comparison tool with no output schema, the description covers the input contract but never indicates what the tool produces (e.g. which total is cheaper or by how much) or the effect of a false 'gleich'/'vollstaendig' flag. Adequate but leaves the agent guessing about the result.

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%: all six parameters have German descriptions plus min/max bounds, so the schema carries the semantics. The description only reinforces that the a_zusatz_eur/b_zusatz_eur values are 'notwendige Zusatzkosten', adding marginal meaning 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 states a specific verb and resource: comparing the delivered purchase totals of two identically equipped quotes including mandatory extra costs. This clearly separates it from neighbouring tools such as angebot_lagerstatus_zitieren or the various *_vergleichen siblings by naming the object of comparison and the cost basis, though it does not name any alternative tool explicitly.

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 qualifier 'gleich ausgestattete' / 'matched quotes', which signals the comparison is only valid for equivalent offers, and the schema's 'gleich' and 'vollstaendig' booleans reinforce this precondition. However, there is no explicit statement of when not to use the tool, what happens if the quotes are unmatched, or which sibling to pick for a different 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