Skip to main content
Glama

getecoback-raumklima

klimafenster_umbauzeit_grenzwert_zwei_plaene

Read-only

Vergleicht belegte Bedienarbeit bei täglichem Abbau mit einem dokumentierten Aufbau für kürzere gemeinsame Nutzung — Compare user handling time for two documented short-term window routines.

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": {
      "tage": "<tage>",
      "auf_und_ab_min": "<auf_und_ab_min>",
      "variante_b_wechselsumme_min": "<variante_b_wechselsumme_min>",
      "variante_b_betrieb_belegt": "<variante_b_betrieb_belegt>"
    },
    "name": "klimafenster_umbauzeit_grenzwert_zwei_plaene"
  }
}

Input Schema

NameRequiredDescriptionDefault
tageYesGeplante Nutzungstage.
auf_und_ab_minYesBeobachtete Bedienzeit für regulären Aufbau plus Abnahme in Minuten.
variante_b_betrieb_belegtYesWaren die Bedingungen für Variante B über alle geplanten Zeiten dokumentiert?
variante_b_wechselsumme_minYesSumme kurzzeitiger, dokumentiert nutzbarer Bedienwechsel in Variante B im selben Zeitraum in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint=true and openWorldHint=false; the description adds that the comparison is against a documented baseline, but not what is returned, how the two variants are weighed, or how the days/scaling factors into the result. With no output schema, the description carries the full burden of explaining the result and fails to do so, which is a real gap for a computation tool.

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 a single short sentence, so there is little waste, but the German and English clauses are near-duplicates rather than complementary, and the structure is not front-loaded toward the purpose (computing a limit value). One language plus the outcome would be tighter.

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?

Four required parameters with no output schema and no description of the computed result means an agent cannot anticipate what it receives or how to interpret a threshold outcome. For a comparison/computation tool this leaves the most important half of the contract unstated.

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 each of the four parameters is already documented, including units (minutes) and bounds. The description adds no extra meaning about how these inputs relate (e.g., whether "tage" scales the comparison), so the baseline 3 applies.

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 description names a specific verb ("Vergleicht" / "Compare") and two things being compared (observed handling time for daily disassembly vs. a documented setup for shorter shared use). However, it never says what the tool actually produces — the name implies a threshold/limit value ("Grenzwert") but the description only says it "compares", leaving the agent unsure whether it computes a verdict, a delta, or a boolean. It is distinct enough from siblings in subject matter but vague on outcome.

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 when-to-use or when-not guidance, and no routing to any of the many sibling comparison tools. The agent must infer applicability from the phrase "short-term window routines" alone, with no conditions or prerequisites 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