Skip to main content
Glama

getecoback-climate-weather

kuehlgeraet_platz_waermeeintrag

Read-only

Kühlgerät am vorgesehenen Platz auf Wärmequellen und freie Gitter prüfen — Identify exposure and vent issues for an existing refrigerator placement.

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": {
      "direkte_sonne": "<direkte_sonne>",
      "waermequelle": "<waermequelle>",
      "gitter_frei": "<gitter_frei>"
    },
    "name": "kuehlgeraet_platz_waermeeintrag"
  }
}

Input Schema

NameRequiredDescriptionDefault
gitter_freiYesRückseitige Lüftungsöffnungen entsprechend der Anleitung frei?
waermequelleYesHerd oder Heizkörper erwärmen unmittelbar den Stellbereich?
direkte_sonneYesDirekte Sonne trifft am Standort regelmäßig auf das Gerät?

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 non-mutating, closed-domain nature is covered. The description adds that this is an exposure/vent issue identification task on an existing placement, but says nothing about what the result looks like (no output schema exists) or how the three assessments are combined.

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?

One compact German sentence with a short English gloss, front-loaded with the resource and the checks to perform. No filler, though the bilingual duplication is slightly redundant for an agent that reads either language.

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?

The tool is simple (three required booleans, fully documented, read-only annotations, no output schema), and the description covers purpose, scope (existing placement) and the checks performed. The only real gap is what the tool reports back, which is minor given the low complexity.

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 each parameter is phrased as a fully worded question, so the schema carries the semantic load. The description reinforces two of the three inputs ('Wärmequellen' for waermequelle, 'freie Gitter' for gitter_frei) but says nothing about direkte_sonne, so it adds only marginal meaning 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 (prüfen/check) and a concrete resource (Kühlgerät am vorgesehenen Platz) and enumerates the two things being checked: heat sources and free vents. The phrase 'for an existing refrigerator placement' distinguishes it from installation-oriented siblings such as kuehlgeraet_einbau_lueftungsabgleich, though the differentiation is implicit rather than stated as a 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?

Usage is implied through 'for an existing refrigerator placement', which signals this applies to already-placed units, and via 'Wärmequellen und freie Gitter' which scopes the check. However, there is no explicit when-to-use / when-not-to-use statement and no named alternative such as the ventilation-balancing or grille-care 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