Skip to main content
Glama

getecoback-climate-weather

mobile_klima_einlagern_check

Read-only

Vor der Winterpause offene Schritte für eine mobile Klimaanlage erkennen — Check portable AC storage readiness against its own manual.

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": {
      "anleitung": "<anleitung>",
      "wasser": "<wasser>",
      "trocken": "<trocken>",
      "lager": "<lager>"
    },
    "name": "mobile_klima_einlagern_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
lagerYesLagerort, Temperatur und Ausrichtung entsprechen den Angaben des Herstellers?
wasserYesKondensat ist nach Herstellerangaben entfernt?
trockenYesFilter und Gerät sind gemäß Anleitung trocken?
anleitungYesAnleitung für das genaue Modell liegt vor?

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 safety and scope are covered structurally. The description adds one meaningful behavioral fact: the checklist is evaluated against the device's own manual, which matters for how the boolean answers should be judged. It says nothing about what the tool returns (a verdict, a list of open steps, a score) or how the four answers combine.

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?

The definition is short and front-loads the seasonal trigger before the English restatement. The German and English sentences convey essentially the same content, which is mild redundancy, but nothing else is wasted and the structure is easy to parse.

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?

For a read-only four-boolean checklist with full schema coverage and no output schema, the definition gives enough to invoke it correctly, and the 'own manual' clause tells the agent how to interpret the answers. Only the return shape of the check remains unspecified, which is a minor gap at this 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%, so all four booleans are documented in the schema itself, which sets the baseline at 3. The description's 'against its own manual' reinforces the intent behind 'anleitung' but adds no meaning beyond the schema's own parameter descriptions.

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?

Uses a specific verb and resource combination: 'Vor der Winterpause offene Schritte für eine mobile Klimaanlage erkennen' and 'Check portable AC storage readiness against its own manual.' An agent can tell this is a pre-storage readiness checklist for a portable AC unit, distinct from maintenance or measurement siblings. It does not name a sibling explicitly, so it stops short of full differentiation.

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 phrase 'Vor der Winterpause' supplies a clear temporal context for when to call it, but there is no guidance on when not to use it or on which sibling handles adjacent checks (e.g. the condensate or filter checks in the sibling list). Usage is implied by the seasonal framing rather than stated as explicit routing.

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