Skip to main content
Glama

getecoback-climate-weather

backofen_vorheizanteil_getrennte_laeufe

Read-only

Bei gleichem Backergebnis den gemessenen Vorheizanteil einer gemeinsamen und zweier getrennter Sitzungen vergleichen — Compare measured preheat shares for one combined session and two separate sessions.

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": {
      "gemeinsam_kwh": "<gemeinsam_kwh>",
      "gemeinsam_vorheizen_kwh": "<gemeinsam_vorheizen_kwh>",
      "getrennt_kwh": "<getrennt_kwh>",
      "getrennt_vorheizen_kwh": "<getrennt_vorheizen_kwh>",
      "gleiche_aufgabe": "<gleiche_aufgabe>"
    },
    "name": "backofen_vorheizanteil_getrennte_laeufe"
  }
}

Input Schema

NameRequiredDescriptionDefault
getrennt_kwhYesGesamtwert der zwei getrennten Sitzungen in kWh.
gemeinsam_kwhYesGesamter Messwert der gemeinsamen Sitzung in kWh.
gleiche_aufgabeYesWaren Menge, geeignetes Programm und angestrebtes Ergebnis vergleichbar?
getrennt_vorheizen_kwhYesDarin enthaltene beide Vorheizphasen zusammen in kWh.
gemeinsam_vorheizen_kwhYesDarin enthaltenes Vorheizen in kWh.

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 nothing is mutated and no external data is fetched; the description adds only that the comparison is conditioned on an identical baking result. It says nothing about what the computation returns (a share, a percentage, a verdict) or how it handles inputs where preheat exceeds the session total.

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 front-loaded sentence with the comparison target stated first. The German and English halves are largely duplicative, which costs a little space but aids a bilingual agent.

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 read-only, closed-world arithmetic tool with five fully documented numeric parameters, the definition plus schema is close to sufficient. The one real gap is the absence of an output schema combined with no description of the result, so the agent cannot tell what form the comparison takes.

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% and every parameter carries a German description, so the schema does the heavy lifting and baseline 3 applies. The description's framing of 'one combined vs two separate sessions' helps map the four kWh parameters to their roles, but adds no units, bounds, or cross-field constraints 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 verb ('vergleichen / compare') and a specific resource ('gemessener Vorheizanteil einer gemeinsamen und zweier getrennter Sitzungen'), so an agent knows this computes a preheat-share comparison rather than measuring or fetching anything. It does not name or exclude any of the many sibling backofen_* tools, so differentiation relies on the name alone.

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 clause 'bei gleichem Backergebnis' implies the prerequisite that comparisons are only meaningful when the baking outcome is equivalent, which is reinforced by the gleiche_aufgabe parameter. However, there is no explicit when-to-use / when-not-to-use statement and no pointer to alternative comparison tools among the siblings.

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