Skip to main content
Glama

getecoback-climate-weather

geraetekauf_raten_gegen_barpreis

Read-only

Ausgewiesene Raten, Schlusszahlung und Gebühren zum Barpreisvergleich addieren — Compare the stated installment total with the full cash price.

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": {
      "bar_eur": "<bar_eur>",
      "anzahlung_eur": "<anzahlung_eur>",
      "anzahl_raten": "<anzahl_raten>",
      "rate_eur": "<rate_eur>",
      "schluss_eur": "<schluss_eur>",
      "gebuehren_eur": "<gebuehren_eur>"
    },
    "name": "geraetekauf_raten_gegen_barpreis"
  }
}

Input Schema

NameRequiredDescriptionDefault
bar_eurYesVollständiger Barpreis für dasselbe Angebot.
rate_eurYesBetrag einer regulären Rate in Euro.
schluss_eurYesSeparate Schlusszahlung in Euro, sonst null Euro.
anzahl_ratenYesAnzahl gleicher vollständiger Raten, ohne Schlusszahlung.
anzahlung_eurYesAusgewiesene Anzahlung in Euro.
gebuehren_eurYesZusätzlich ausgewiesene Gebühren in Euro.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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-domain pure computation. The description adds the comparison framing (total outlay vs. cash price) but does not state what the output represents, whether the comparison is a delta or ratio, or any rounding/currency assumptions. With annotations covering safety, a 3 fits.

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, front-loaded with the computational formula followed by the comparison purpose. No filler, though the bilingual duplication spends words restating the same idea rather than adding information.

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 six-required-parameter arithmetic tool with no output schema, the description conveys the inputs' role and the comparison intent, and the schema carries all per-parameter detail. What it lacks is a statement of the returned quantity, which matters since there is no output schema to explain 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%: every parameter has a clear German description including bounds (e.g. anzahl_raten max 120, schluss_eur 'sonst null Euro'). The description adds the aggregation concept (Raten + Schlusszahlung + Gebühren) but no parameter-level meaning beyond the schema, so 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: adding installments, final payment and fees to compare against a cash price. The German phrase plus English gloss makes the verb+resource clear (installment total vs. cash price). It does not explicitly differentiate itself from sibling comparison tools, but the domain is unambiguous.

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 description implies usage — compare stated installment total with full cash price — but gives no explicit when-to-use criteria, no prerequisites, and no named alternative tool. Usage is inferable from the purpose statement 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