Skip to main content
Glama

getecoback-raumklima

stromtarif_vorauszahlung_kapital

Read-only

Kapitalbindung einer Vorauszahlung gegenüber Monatszahlungen abschätzen. — Estimate the opportunity cost of paying a full year up front.

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": {
      "voraus_eur": "<voraus_eur>",
      "monat_eur": "<monat_eur>",
      "rechenzins_prozent": "<rechenzins_prozent>"
    },
    "name": "stromtarif_vorauszahlung_kapital"
  }
}

Input Schema

NameRequiredDescriptionDefault
monat_eurYesPreis einer konstanten Monatszahlung in Euro.
voraus_eurYesGesamter heute im Voraus fälliger Preis in Euro.
rechenzins_prozentYesSelbst gewählter jährlicher Vergleichszins in Prozent.

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, making clear this is a pure local computation with no side effects. The description adds that the output is an estimate of opportunity cost, but says nothing about assumptions, rounding, or what the computed figure represents beyond that. With annotations carrying the safety profile, this is adequate but thin.

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 sentences with the core concept front-loaded; no filler. The German/English duplication is mild redundancy but the English line genuinely clarifies the intent rather than restating the name.

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 three-parameter, fully documented, read-only calculator with no output schema, the definition supplies enough to call it correctly: what it computes, the inputs' meaning, and the comparison framing. Only the exact form of the returned figure is left implicit, which is minor for a simple arithmetic tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each parameter is fully documented with ranges, so the schema does the heavy lifting. The description still adds interpretive meaning — 'paying a full year up front' maps to voraus_eur and 'opportunity cost' explains the role of the self-chosen comparison rate — which is a modest but real contribution beyond the schema.

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 concept — the capital lock-up / opportunity cost of paying a year's electricity price up front versus monthly installments — which is a clear verb-plus-resource for a calculator. It is not tautological and an agent can see it belongs to the tariff-comparison family, though it does not explicitly contrast itself with siblings such as stromtarif_teilgarantie_szenario.

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 only implied: the phrase 'gegenüber Monatszahlungen' tells the reader it is a comparison scenario, so an agent can infer it is used when weighing prepayment against monthly billing. There is no explicit when-to-use, when-not-to-use, or named alternative tool.

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