Skip to main content
Glama

getecoback-climate-weather

messreihe_konstante_anzeige_kontrollwechsel

Read-only

Gleichbleibende Sensorwerte nach einem unabhängig beobachteten Kontrollwechsel prüfen — Screen a flat trace against a documented above-resolution reference change.

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": {
      "spannweite_anzeige": "<spannweite_anzeige>",
      "spannweite_referenz": "<spannweite_referenz>",
      "kleinster_sichtbarer_schritt": "<kleinster_sichtbarer_schritt>",
      "messfenster_gleich": "<messfenster_gleich>"
    },
    "name": "messreihe_konstante_anzeige_kontrollwechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
messfenster_gleichYesSind Messgröße, Ort, Zeit und Reaktionszeit für die Kontrolle vergleichbar?
spannweite_anzeigeYesSpannweite der aufgezeichneten Werte in einer einheitlichen Einheit.
spannweite_referenzYesAn demselben Ort gemessene Referenzspannweite in derselben Einheit.
kleinster_sichtbarer_schrittYesDokumentierte Anzeigestufe der geprüften Messgröße.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 is covered and the description is not obliged to restate it. The description adds the substantive behavioral idea that the reference change must be above the display resolution, which tells the agent why the call can legitimately conclude "no real change." It still says nothing about the shape of the result (a verdict, a text justification, a pass/fail flag) despite there being no output schema, and nothing about how a false messfenster_gleich is handled.

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?

It is a single tight sentence with the trigger condition front-loaded followed by the operative comparison, and zero filler. The bilingual duplication (German plus English rendering) is mildly redundant but aids comprehension rather than obscuring the point.

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?

With four required numeric parameters at full schema coverage and readOnly annotations, the definition is close to sufficient: the agent knows the inputs and the screening intent. The remaining gap is that with no output schema the agent cannot anticipate the return shape or the meaning of the verdict, which matters for a decision-style tool.

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 schema already explains all four parameters, and the baseline of 3 applies. The description does add relational meaning the schema alone does not make explicit: the reference span is meant to be compared against the smallest visible step, and the recorded span is expected to be flat. That is a modest but real contribution beyond the field-level text.

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 concrete verb ("prüfen"/"screen") and a concrete object ("Gleichbleibende Sensorwerte" / "flat trace") tied to a specific precondition (an independently observed control change) and a specific comparison (a documented above-resolution reference change). That is enough to distinguish it from generic measurement-series siblings, but it never names which sibling would apply when the trace is not flat or when no control change was observed.

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 phrase "nach einem unabhängig beobachteten Kontrollwechsel" implies the trigger condition (a control change was observed independently of the sensor), which is useful implied usage guidance. However, there is no explicit when-to-use vs when-not, no routing to alternatives such as the repetition-counting or outlier siblings, and no statement about what to do when messfenster_gleich is false.

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