Skip to main content
Glama

getecoback-raumklima

stromtarif_bonus_bedingungen_check

Read-only

Bei einem Neukundenbonus offene Bedingungen und den Unterschied bei ausbleibender Zahlung sichtbar machen. — Identify unresolved bonus conditions before budgeting a conditional credit.

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": {
      "kosten_ohne_bonus": "<kosten_ohne_bonus>",
      "bonus_eur": "<bonus_eur>",
      "bezugsdauer_ok": "<bezugsdauer_ok>",
      "kundenstatus_ok": "<kundenstatus_ok>",
      "weitere_bedingungen_ok": "<weitere_bedingungen_ok>"
    },
    "name": "stromtarif_bonus_bedingungen_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
bonus_eurYesEinmaliger Bonus in Euro laut Angebot.
bezugsdauer_okYesVorgeschriebene tatsächliche Belieferungsdauer wurde oder wird belegbar erfüllt.
kundenstatus_okYesBedingung zum Neukundenstatus ist anhand der Tarifunterlagen geprüft.
kosten_ohne_bonusYesKosten im ersten Tarifjahr ohne Bonus in Euro.
weitere_bedingungen_okYesWeitere Bonusbedingungen und die Auszahlung sind anhand der Unterlagen geprüft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 safety is covered and the description only needs to add nuance. It confirms the tool surfaces unresolved conditions rather than resolving them, but it does not say what the result contains or how the cost/bonus figures are combined, so the added context is thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loaded, but the em-dash followed by an English restatement of the same idea is redundant rather than additive. The second sentence could have spent its space on output or parameter semantics instead of translating the first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description never says what the check returns (a flagged set of open conditions? a euro delta?). With five required inputs driving a computation, the agent cannot predict the response shape, and the key phrase 'Unterschied bei ausbleibender Zahlung' is left unexplained.

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% with five clearly documented parameters, so the schema carries the semantics and baseline 3 applies. The description adds no interpretation of how kosten_ohne_bonus, bonus_eur and the three boolean checks interact in the result.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The German sentence names the domain (Neukundenbonus) and the action (offene Bedingungen sichtbar machen), so an agent gets the general idea. But 'den Unterschied bei ausbleibender Zahlung sichtbar machen' is ambiguous — the difference between what and what is never stated, and nothing distinguishes it from the sibling stromtarife_bonus_vergleichen.

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?

'before budgeting a conditional credit' gives a timing cue for when to call it, which is real guidance. There are no exclusions, no prerequisites about which documents must be checked first, and no routing away from the sibling comparison 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