Skip to main content
Glama

getecoback-raumklima

kuehlschrank_griffseite_routinenvergleich

Read-only

Zwei vor Ort geprüfte Anordnungen anhand der nötigen Umgehungen am Kühlschrank vergleichen — Compare how often a measured refrigerator door routine requires walking around the door.

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": {
      "oeffnungen_pro_tag": "<oeffnungen_pro_tag>",
      "umgehungen_a": "<umgehungen_a>",
      "umgehungen_b": "<umgehungen_b>",
      "gleichtag": "<gleichtag>"
    },
    "name": "kuehlschrank_griffseite_routinenvergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
gleichtagYesSind Aufteilung, Nutzung und Beobachtungsumfang vergleichbar?
umgehungen_aYesDavon nötige Umgehungen bei einer geprüften Anordnung A.
umgehungen_bYesDavon nötige Umgehungen bei einer geprüften Anordnung B.
oeffnungen_pro_tagYesBeobachtete Zahl der vergleichbaren täglichen Öffnungen.

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 known. The description adds that inputs must be 'vor Ort geprüfte' (verified on-site) arrangements and that detours are 'nötig' (required), which is useful qualification, but it says nothing about the comparison logic, thresholds, or what a result means.

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 pair, so nothing is bloated. However, the English half is a loose gloss rather than a translation and repeats the German content without adding the operational detail an agent needs.

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?

For a read-only, self-contained computation with full schema coverage this is minimally adequate. With no output schema, the description should have stated what the comparison returns (counts, difference, or recommendation), which is the main missing piece.

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 its own German description, so the baseline is 3. The description reinforces that umgehungen_a/b are necessary detours under each arrangement and that gleichtag is a comparability guard, but adds no format or constraint 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 concrete verb (compare) and resources (two on-site verified arrangements), and ties the comparison to a specific measure — necessary walk-arounds (Umgehungen) at the refrigerator. It is distinguishable from siblings like kuehlschrank_einraeumfolge or kuehlschrank_temperaturprotokoll, but what the comparison actually produces (a delta, a ratio, a verdict) stays vague.

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 or when-not-to-use guidance and no named alternative. Only an implicit condition is inferable: call it when you have two measured configurations. Nothing tells the agent how this differs from the other kuehlschrank_* routines in practice.

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