Skip to main content
Glama

getecoback-climate-weather

sparaussage_bis_zu_referenzwert

Read-only

Eine maximale Werbe-Ersparnis mit dokumentiertem Bezugswert und eigener Messung einordnen — Interpret an up-to savings claim against its stated baseline.

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": {
      "maximal_prozent": "<maximal_prozent>",
      "referenz_kwh": "<referenz_kwh>",
      "beobachtet_kwh": "<beobachtet_kwh>",
      "bedingungen_gleich": "<bedingungen_gleich>"
    },
    "name": "sparaussage_bis_zu_referenzwert"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenz_kwhYesVerbrauch der ausdrücklich zugehörigen Referenz in kWh.
beobachtet_kwhYesVerbrauch bei der beobachteten Alternative in kWh.
maximal_prozentYesBeworbene Obergrenze in Prozent.
bedingungen_gleichYesGleiche Wärmeaufgabe, Nutzungsdauer und passende Bedingungen belegt?

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?

The readOnlyHint=true and openWorldHint=false annotations already establish this as a safe, closed-world read, so the description carries a lighter burden. It adds that the interpretation hinges on a documented reference, which is useful context, but it never says what the assessment produces (a verdict, a computed delta, a plausibility flag) and there is no output schema to fill that 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?

A single bilingual sentence that front-loads the claim type and the baseline, with no filler. The German/English duplication is redundant for a reader of one language but small in absolute cost.

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?

With four required numeric/boolean parameters and no output schema, the definition explains the inputs well but leaves the result of the interpretation entirely unspecified. For a tool whose sole value is producing an assessment, that is a meaningful gap, though annotations cover the safety profile.

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%, so all four parameters are already fully documented, including the meaning of the reference and observed consumption. The description echoes the concepts of baseline ('Bezugswert') and own measurement ('eigene Messung') but adds no formatting, unit, or edge-case detail beyond the schema, so the 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 gives a concrete verb ('einordnen' / interpret) and a precisely scoped resource: an up-to savings claim measured against its stated baseline plus one's own measurement. That is enough to tell it apart from unrelated siblings such as measurement or quoting tools. It stops short of explicitly naming what it is not, so it lands at 4 rather than 5.

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 wording 'mit dokumentiertem Bezugswert und eigener Messung' implies the precondition for calling it (a documented baseline and an own observation), but there is no explicit when-to-use / when-not-to-use statement and no named alternative. Usage is inferable 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