Skip to main content
Glama

getecoback-climate-weather

wasserkocher_twk8613p_hoehenlage_2000_aufsicht

Read-only

Prüft Höhenlage und beaufsichtigte Nutzung für Bosch TWK8613P im geplanten Haushalt — Verify the documented altitude and observation conditions for the proposed use site.

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_zugeordnet": "<anleitung_zugeordnet>",
      "hoehe_belegt": "<hoehe_belegt>",
      "meter": "<meter>",
      "beaufsichtigt": "<beaufsichtigt>"
    },
    "name": "wasserkocher_twk8613p_hoehenlage_2000_aufsicht"
  }
}

Input Schema

NameRequiredDescriptionDefault
meterYesHöhe über dem Meeresspiegel in Metern.
hoehe_belegtYesHöhenlage des konkreten Haushalts ist für die Entscheidung bekannt.
beaufsichtigtYesBeaufsichtigung während des geplanten Gebrauchs ist organisatorisch belegt.
anleitung_zugeordnetYesDas Gerät ist als deutsches TWK8613P identifiziert und die angegebene TWK86-Anleitung über die E-Nummer zugeordnet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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, and "Prüft/Verify" is consistent with a safe read-only evaluation. The description adds that it concerns documented altitude and observation conditions at a proposed site, but withholds the decision logic and the thresholds (notably the 2000 m limit in the name) and says nothing about what a failed check looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded with the object of the check, but the German sentence is immediately repeated in English, duplicating the same content and adding tokens without adding information.

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 four-required-parameter read-only verification tool with no output schema, the description conveys enough that an agent knows what is being validated and against which site. The main remaining gap is that the outcome semantics and thresholds are not stated.

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 parameters including the enum "beaufsichtigt" are already documented, making 3 the baseline. The description only loosely gestures at the parameters ("documented altitude," "observation conditions") and adds no semantics beyond the schema, such as how the four inputs combine.

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 gives a specific verb ("Prüft/Verify") and specific subjects ("Höhenlage und beaufsichtigte Nutzung") scoped to one device model (Bosch TWK8613P) and one site ("geplanten Haushalt"). It is clearly a check/validation tool rather than an action tool, though it never says what the check yields (verdict, boolean, error).

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 only implied: an agent can infer this is for confirming altitude and supervision conditions of a proposed use site. There is no explicit when-to-use vs. when-not guidance, no prerequisites, and no reference to any alternative check despite many similar sibling tools.

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