Skip to main content
Glama

getecoback-climate-weather

lb55_dampfstufe_mengenbezug

Read-only

Rechne die deklarierte Dampfstufe des Beurer LB 55 auf eine geplante Laufzeit um — Convert the documented LB 55 steam setting to a runtime quantity

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": {
      "artikel_68605": "<artikel_68605>",
      "dampfstufe": "<dampfstufe>",
      "laufminuten": "<laufminuten>"
    },
    "name": "lb55_dampfstufe_mengenbezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
dampfstufeYesAuf der Geräteanleitung ausgewiesene Stufe
laufminutenYesVorgesehene aktive Laufzeit in Minuten
artikel_68605YesArt.-Nr. 68605 des Beurer LB 55 am konkreten Gerät abgeglichen

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, so the agent knows this is a closed-world read/compute call. The description adds that the input is a documented device setting being projected onto a planned runtime, but it does not state that the result is a deterministic arithmetic derivation, does not give output units, and does not explain that artikel_68605 acts as a verification gate. Useful context, but thin 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 that puts the operation and the device first. The German/English duplication is mildly redundant, but it keeps terminology aligned with the parameter names at low cost, so little is wasted overall.

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?

For a simple three-required-parameter computation with no output schema, the description should say what the returned quantity is and in what unit, which it does not. It also leaves the role of the required artikel_68605 boolean unaddressed. The core intent is clear, but an agent still cannot predict the shape of the answer.

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 the enum values (200_ml_h, 400_ml_h), the 0–1440 minute bound, and the meaning of artikel_68605 are already documented in the schema. The description reinforces that dampfstufe is the device-documented level and laufminuten the planned active runtime, but adds no interpretation of the article-number check or how the rate is applied. Baseline 3 is appropriate when the schema carries the parameter burden.

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 concrete verb (convert/rechnen ... um) and a concrete resource: the documented Beurer LB 55 steam setting tied to a planned runtime. The device-specific framing distinguishes it from generic humidifier siblings such as befeuchter_tank_laufzeit. It falls short of 5 because the resulting quantity is only described vaguely as 'a runtime quantity' — it never says whether the output is milliliters of water, liters, or a runtime figure.

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: the agent can infer it applies when a declared steam setting and a planned run time are known. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative among the many humidifier/runtime siblings. Nothing is misleading, but the agent must infer the selection criterion.

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