Skip to main content
Glama

getecoback-climate-weather

kuehlgeraet_fachvolumen_bedarfsabgleich

Read-only

Eigenen Platzbedarf in Kühl- und Gefrierfach getrennt mit den dokumentierten Nutzvolumina abgleichen — Identify the actual compartment capacity shortfall rather than combining both figures.

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": {
      "kuehlfach_nutz_l": "<kuehlfach_nutz_l>",
      "gefrierfach_nutz_l": "<gefrierfach_nutz_l>",
      "eigene_kuehlboxen_l": "<eigene_kuehlboxen_l>",
      "eigene_gefrierboxen_l": "<eigene_gefrierboxen_l>",
      "getrennt_ausgewiesen": "<getrennt_ausgewiesen>"
    },
    "name": "kuehlgeraet_fachvolumen_bedarfsabgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
kuehlfach_nutz_lYesNutzvolumen des Kühlfachs laut Datenblatt des genauen Modells.
gefrierfach_nutz_lYesNutzvolumen des Gefrierfachs laut Datenblatt des genauen Modells.
eigene_kuehlboxen_lYesGemessenes beanspruchtes Volumen der fürs Kühlfach vorgesehenen Behälter.
getrennt_ausgewiesenYesBeide Nutzvolumina sind für die konkreten Fächer getrennt dokumentiert.
eigene_gefrierboxen_lYesGemessenes beanspruchtes Volumen der fürs Gefrierfach vorgesehenen Behälter.

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?

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so no extra credit is needed for declaring this a pure read/compute. The description adds useful framing about the separation logic but does not say what the result looks like, nor what happens when 'getrennt_ausgewiesen' is false — a refusal, a fallback, or a partial comparison — which is the main behavioral branch of this tool.

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?

Two tightly packed clauses with no filler, and the corrective guidance (separate rather than combined) is front-loaded after the core action. The German/English doubling is mildly redundant but each version adds something, so no real waste.

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, fully described parameters and no output schema, the description covers the input side adequately. It is incomplete on the output side — nothing on whether the shortfall is returned per compartment, in liters, or as a verdict — and it ignores the boolean gate parameter, which is central to correct invocation.

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 every one of the five parameters is already fully documented in the schema, including the distinction between datasheet Nutzvolumen and measured container volume. The description reinforces the separated treatment but adds no format, unit, or validation detail beyond the schema; 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 names a specific action (abgleichen) and specific resources (eigener Platzbedarf vs. dokumentierte Nutzvolumina in Kühl- und Gefrierfach) and explicitly rules out the naive aggregation of both compartments. An agent can tell it performs a per-compartment capacity comparison. It stops short of 5 because it does not name the sibling tool that does the combined-figure comparison.

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 English clause gives a clear usage steer: determine the compartment-specific shortfall instead of merging the two figures. However, there is no statement of preconditions or when-not to use it, notably that the required flag 'getrennt_ausgewiesen' encodes a hard prerequisite (per-compartment datasheet values), which the description never mentions.

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