Skip to main content
Glama

getecoback-climate-weather

wqg241001_tank_oder_ablauf_platzentscheidung

Read-only

Den geplanten Umgang mit Kondenswasser an der Bosch-Säule als Tank- oder dokumentierten Ablaufpfad prüfen — Distinguish user access from an independently verified drainage configuration.

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": {
      "wqg241001_belegt": "<wqg241001_belegt>",
      "modus": "<modus>",
      "tankfuehrung_erreichbar": "<tankfuehrung_erreichbar>",
      "ablauf_passend_bestaetigt": "<ablauf_passend_bestaetigt>"
    },
    "name": "wqg241001_tank_oder_ablauf_platzentscheidung"
  }
}

Input Schema

NameRequiredDescriptionDefault
modusYesDer aktuell nachweislich geplante Kondenswasserweg.
wqg241001_belegtYesIst das Gerät nach seinem eigenen Typenschild Bosch WQG241001?
tankfuehrung_erreichbarYesGriff und ganzer Behälterweg am Standort geometrisch abgeglichen.
ablauf_passend_bestaetigtYesExaktes Zubehör und die konkrete Anschlussplanung laut Unterlagen überprüft, falls direkter Ablauf vorgesehen.

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 clear. The description adds that this is an evidence/verification check and distinguishes user access from independently verified drainage, but it does not describe outputs, error handling, or preconditions.

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 one compact sentence with the core check front-loaded and no filler. The bilingual dash construction is slightly dense but remains efficient and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with four required enum parameters and no output schema, the definition does not explain what a check returns or how conflicting values should be resolved. The schema documents each field, but the overall decision workflow remains underspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds a meaningful interpretation rule: separate user access from independently verified drainage configuration, which helps map the enum fields. It still does not discuss individual parameters or value interactions, so it is not a 5.

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 verification action ('prüfen') on a specific resource: planned condensate handling as a tank or documented drain path. It also frames the distinction between user access and independently verified drainage configuration. It lacks explicit sibling differentiation and contains some opaque terminology, so it is clear but not fully self-distinguishing.

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 or when-not-to-use guidance, and no alternative tools are named. The distinction clause is a verification criterion rather than a tool-selection rule, leaving the agent to infer when this tool applies.

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