Skip to main content
Glama

getecoback-raumklima

geraetewechsel_co2_szenario_schwelle

Read-only

Eigene Betriebs- und Herstellungswerte für einen eng abgegrenzten Geräteaustausch vergleichen — Estimate when documented operating emissions could offset extra production emissions.

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": {
      "ersparnis_kwh_jahr": "<ersparnis_kwh_jahr>",
      "betriebsfaktor_kg_kwh": "<betriebsfaktor_kg_kwh>",
      "mehr_herstellung_kg": "<mehr_herstellung_kg>",
      "jahre": "<jahre>",
      "grenzen_gleich": "<grenzen_gleich>"
    },
    "name": "geraetewechsel_co2_szenario_schwelle"
  }
}

Input Schema

NameRequiredDescriptionDefault
jahreYesGewählter Zeitraum in Jahren.
grenzen_gleichYesVergleichbare Aufgabe und kompatible Emissionsgrenzen belegt?
ersparnis_kwh_jahrYesDokumentierte jährliche Stromersparnis bei gleicher Nutzung in kWh, negatives Vorzeichen bei Mehrverbrauch.
mehr_herstellung_kgYesZusätzliche dokumentierte Herstellungswirkung des Ersatzes in kg CO2e.
betriebsfaktor_kg_kwhYesVom Nutzer belegter Emissionsfaktor in kg CO2e je kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety profile is covered and the description only needs to add context. It does add that inputs must be user-documented and that the scenario is deliberately narrow, but it stays silent on what the result looks like and on what happens when grenzen_gleich is false.

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?

It is short, but the German/English mix and the vague qualifier 'eng abgegrenzten' make the intent harder to parse than necessary. The core question is present but not front-loaded as a crisp verb-plus-outcome statement.

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 five required parameters, no output schema and only minimal annotations, the definition is adequate but thin: it never explains the returned threshold, the effect of the grenzen_gleich flag, or the valid input ranges already bounded in the schema. An agent could call it, but not confidently interpret the outcome.

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%, so the schema already documents every parameter including sign conventions for negative savings. The description only reinforces that the values must be documented and user-supplied, adding no format or interpretation detail 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 action (compare one's own operating and manufacturing figures for a narrowly scoped device replacement) and states the underlying question — when documented operating emissions could offset the extra production emissions. An agent can infer it computes a break-even point, though it never explicitly says a threshold year value is returned, and it does not name how it differs from the sibling geraetewechsel_rechnen.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no statement of prerequisites beyond the word 'documented', and no contrast with alternative tools such as the general device-replacement calculation sibling. Usage is only implied by the narrow-scope wording.

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