Skip to main content
Glama

getecoback-raumklima

betriebszustand_stichprobe_display_status_muster

Read-only

Bei mehreren Geräteabschnitten mit gleichem Symbol prüfen, ob bestätigte Funktionen den Abschnitt trotzdem unterschiedlich einordnen — Expose when one display symbol groups multiple actual operating states.

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": {
      "abschnitte_mit_symbol": "<abschnitte_mit_symbol>",
      "belegte_aus_abschnitte": "<belegte_aus_abschnitte>",
      "belegte_bereitschafts_abschnitte": "<belegte_bereitschafts_abschnitte>"
    },
    "name": "betriebszustand_stichprobe_display_status_muster"
  }
}

Input Schema

NameRequiredDescriptionDefault
abschnitte_mit_symbolYesZahl aller unterschiedlich abgegrenzten Beobachtungsabschnitte mit exakt demselben Symbol.
belegte_aus_abschnitteYesDavon unabhängig als Aus-Zustand dokumentierte Abschnitte.
belegte_bereitschafts_abschnitteYesDavon andere, unabhängig als Bereitschaft dokumentierte Abschnitte.

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 safety and scope are covered structurally. The description adds that the tool compares confirmed classifications against symbol grouping and exposes discrepancies, which is real behavioral context. It does not say what the result contains (no output schema exists), e.g. whether it returns a boolean flag, a ratio, or a list of offending sections, nor does it mention thresholds or edge cases such as zero matching sections.

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 two short clauses, front-loaded with the condition and followed by the outcome, so an agent can scan it quickly. The main inefficiency is that the German and English halves restate the same idea rather than adding complementary information.

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?

With three required, fully documented numeric parameters and no output schema, the description carries the burden of explaining the result semantics, and it does not: it never states what the tool returns or how the three counts are combined into an exposure judgment. For a pure computation tool this leaves a meaningful gap an agent would need to discover by trial.

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 description coverage is 100%, so the baseline is 3, and the description corroborates the semantics of the three counts, clarifying that the counts are compared to determine whether the same symbol spans differing operating states. It does not, however, explain how the off-state and standby counts combine or what ratio triggers the exposure, so it only modestly exceeds the schema.

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 operation – detecting when confirmed function classifications assign different operating states to sections sharing one display symbol, i.e. "Expose when one display symbol groups multiple actual operating states." That is a specific, non-tautological purpose an agent can recognize. It stops short of differentiating itself from the many sibling betriebszustand_* tools, so it is not a 5.

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?

The German clause embeds an implicit precondition ("Bei mehreren Geräteabschnitten mit gleichem Symbol" – only relevant when several sections share the same symbol), which gives the agent a usable trigger. However, there is no explicit when-not guidance, no prerequisites about data collection, and no pointer to alternatives among the numerous 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