Skip to main content
Glama

getecoback-raumklima

klimageraet_kondenswasser_check

Read-only

Sichtbare Kondenswasserprobleme am mobilen Klimagerät einordnen — Triage visible condensate leaks and identify when to stop using the appliance.

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": {
      "ort": "<ort>",
      "tank_voll": "<tank_voll>",
      "wiederkehrend": "<wiederkehrend>"
    },
    "name": "klimageraet_kondenswasser_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
ortYesWo tritt das Wasser aus?
tank_vollYesDas Gerät meldet vollen Tank?
wiederkehrendYesDas Problem bleibt nach den im Handbuch vorgesehenen Kontrollen bestehen?

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 safety profile is covered. The description adds that the tool judges when to stop operating the appliance, which is meaningful behavioral context, but it does not say what the triage yields or how the leak location drives the verdict.

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 resource scoping first and the safety outcome second; no filler. The bilingual restatement is slightly redundant but serves clarity for mixed-language agents.

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 three-boolean/enum triage tool with fully documented parameters and no output schema, the description supplies enough to select and call it. The only gap is what the classification response looks like.

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% with clear German labels including an enum for leak location, so the schema carries the parameter burden. The description adds no interpretation of the three inputs (location, full tank, recurrence) or how they combine, so 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?

Names a specific verb ('einordnen'/triage) and resource ('Sichtbare Kondenswasserprobleme am mobilen Klimagerät'), plus a secondary safety goal (identify when to stop using). An agent can distinguish this from tank-emptying or siting checks among the siblings, though no sibling is named explicitly.

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 by 'sichtbare Kondenswasserprobleme' (visible leaks only) and the stop-use framing, which tells the agent this is a safety triage step. There is no explicit when-not guidance or pointer to the related tank/condensate-drain checks that a user might actually need.

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