Skip to main content
Glama

getecoback-climate-weather

bosch_bfl524_einbaumoebel_hitzebestaendigkeit_luftweg_belege

Read-only

Hitzebeständigkeit von Einbaumöbel und Nachbarfront sowie freigehaltene Lüftungsöffnungen getrennt abgleichen — Check documented furniture temperatures and unobstructed ventilation.

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": {
      "handbuch_belegt": "<handbuch_belegt>",
      "korpus_grad": "<korpus_grad>",
      "front_grad": "<front_grad>",
      "lueftung": "<lueftung>"
    },
    "name": "bosch_bfl524_einbaumoebel_hitzebestaendigkeit_luftweg_belege"
  }
}

Input Schema

NameRequiredDescriptionDefault
lueftungYesPlanung der Lüftungsöffnungen.
front_gradYesDokumentierte Hitzebeständigkeit benachbarter Fronten in °C, 0 falls ungeklärt.
korpus_gradYesDokumentierte Hitzebeständigkeit des Möbelkorpus in °C, 0 falls ungeklärt.
handbuch_belegtYesGenaue deutsche Geräteausführung BFL524MS0 und Anwendbarkeit des Dokuments 9001610906_F am Gerät geklärt?

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 safe, closed-world read profile is covered. The description adds that this is a documented-evidence reconciliation across three separate aspects, but never says what the result looks like (verdict, list of gaps, threshold breach) or what happens when a value is unknown. Useful context, but shallow beyond the annotations.

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 naming the three checked aspects first, followed by an English gloss. The bilingual duplication is slightly redundant but aids disambiguation; nothing is padded or buried.

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?

All four required parameters are fully described in the schema and there is no output schema to compensate for. Still, for a verification tool the description should state what a check yields and how the documented-manual precondition gates the result; neither is covered, leaving the outcome semantics implicit.

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 ranges, enum values, and the meaning of 0 as 'ungeklärt' all documented in the schema itself. The description merely restates the domains (furniture temperatures, ventilation) and adds no handling rules, e.g. whether 0 short-circuits the check or whether handbuch_belegt=false blocks the comparison. Baseline 3 applies since the schema does the semantic work.

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?

States a specific verb (abgleichen / check) and specific resources: documented heat resistance of built-in furniture and neighbouring fronts, plus unobstructed ventilation openings, each compared separately. The three-part scope is explicit. It does not, however, distinguish itself from neighbouring 'belege' checks in the sibling list, so an agent can't tell from the text alone why it should pick this over a related clearance check.

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?

The word 'getrennt' implies the three aspects are compared independently rather than as one verdict, which is mild procedural guidance. Beyond that there is no when-to-use, no when-not-to-use, no named alternative, and no statement of what a failed comparison means for the installation decision.

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