Skip to main content
Glama

getecoback-climate-weather

led_dimmen_minimum_start_schon_leuchtend

Read-only

Bei einer vorhandenen, bereits beobachteten Kombination den niedrigsten stabilen Wert nach Start vom niedrigsten Einschaltwert trennen — Distinguish low-level restart from dimming an already operating lamp.

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": {
      "bedarf_untergrenze_prozent": "<bedarf_untergrenze_prozent>",
      "minimal_laufend_prozent": "<minimal_laufend_prozent>",
      "minimal_start_prozent": "<minimal_start_prozent>",
      "selbe_lichtskala_bestaetigt": "<selbe_lichtskala_bestaetigt>"
    },
    "name": "led_dimmen_minimum_start_schon_leuchtend"
  }
}

Input Schema

NameRequiredDescriptionDefault
minimal_start_prozentYesNiedrigster Wert, bei dem sie laut Beobachtung aus dem ausgeschalteten Zustand stabil anlief.
minimal_laufend_prozentYesNiedrigster stabil belegter Wert, nachdem die Lampe bereits leuchtete.
bedarf_untergrenze_prozentYesEigene gewünschte niedrigste Stufe in Prozent der dokumentierten Lichtskala.
selbe_lichtskala_bestaetigtYesSelbe Lampe, Dimmer, Lampenzahl, Messbasis und vergleichbare Bedingungen in den vorhandenen Beobachtungen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 safe local computation. The description adds the conceptual framing of what distinction is being drawn, which is real behavioral content. It does not disclose what the tool returns or how a conflict between the two thresholds is resolved, which matters for a tool with no output schema.

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 compact sentence with a German statement followed by an English gloss; the precondition is front-loaded and there is no filler. The dense nominal style slightly hurts readability but nothing is redundant.

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?

Four required parameters, no output schema, and the description never says what result comes back or how the two values plus the confirmation flag are combined. For a comparison/decision tool with an undocumented return, this leaves a significant gap the agent must guess at.

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% and all four properties carry precise German descriptions, so the schema does the semantic work. The description mentions the two threshold concepts but adds no units, defaults, or interaction rules beyond what the schema already states. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a domain operation — separating the minimum stable running value from the minimum turn-on value — and the English half clarifies the intent ('distinguish low-level restart from dimming an already operating lamp'). However, it never states the actual action or output; 'trennen' is abstract and an agent cannot tell whether the tool computes, compares, or reports the two thresholds. It is distinguishable from the LED sibling tools by topic but not by operation.

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 only guidance is the precondition 'Bei einer vorhandenen, bereits beobachteten Kombination', which implies observed data must exist before calling. There is no statement of when this tool should be chosen over the many neighboring LED measurement/label tools, and no when-not guidance or named alternative.

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