Skip to main content
Glama

getecoback-climate-weather

luftkuehler_kuehlakku_einsatzgrenzen_belegt

Read-only

Prüft ob genau dieser Kühlakku für den konkreten Tank und Einsatz beschrieben ist — Verify whether this specific cooling pack and its intended placement are documented.

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": {
      "modell": "<modell>",
      "akku": "<akku>",
      "einlage": "<einlage>"
    },
    "name": "luftkuehler_kuehlakku_einsatzgrenzen_belegt"
  }
}

Input Schema

NameRequiredDescriptionDefault
akkuYesBeleg für genau diesen Akku.
modellYesStimmen Gerät und Tankvariante mit der Anleitung überein?
einlageYesDie Einsatzposition für die beabsichtigte Betriebsart ist beschrieben.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 covered structurally. The description adds the meaningful nuance that this is a documentation/evidence check rather than a physical measurement, but it does not say what result the check yields when something is undocumented or how a partial match is treated.

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 German original followed by an English rendering, so the core check is visible immediately. The bilingual duplication is arguably redundant but does not obscure the purpose or pad the text meaningfully.

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 three required boolean/enum parameters, full schema coverage, and readOnly annotations, most call mechanics are covered elsewhere. What is missing is the return semantics: there is no output schema and the description never states whether the tool answers with a yes/no verification, a list of gaps, or a cited reference, which matters for a pure verification tool.

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 coverage is 100%, so all three parameters (akku, modell, einlage) are already documented in the schema, including the enum for akku. The description only loosely maps its phrasing ('genau dieser Kühlakku', 'konkreter Tank', 'Einsatz') onto those fields, adding no format or edge-case semantics 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 states a specific verb and object: it verifies whether a specific cooling pack and its intended placement are documented for a concrete tank/use case. That is more precise than a tautology, but it draws no boundary against the many similarly named siblings (e.g. luftkuehler_kuehlakku_pegelversatz_tank or luftkuehler_kuehlakku_vor_nach_gegen_wasserprobe), so an agent cannot tell from the text alone which check applies.

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 guidance, no stated preconditions (e.g. when a documentation record exists versus when a measurement is needed), and no named alternative. Usage is only implied by the phrase 'für den konkreten Tank und Einsatz', leaving the agent to infer the scenario.

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