Skip to main content
Glama

getecoback-climate-weather

dachraum_messreihe_vorhang_zwei_ruecknahmeproben

Read-only

Prüfe, ob ein beobachteter Temperaturvorteil beim Rückwechsel der Beschattung erneut verloren ging — Check whether reversing a shading change also reversed the observed temperature movement

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": {
      "start_ohne_c": "<start_ohne_c>",
      "zwischen_mit_c": "<zwischen_mit_c>",
      "zurueck_ohne_c": "<zurueck_ohne_c>",
      "aenderungsgrenze_c": "<aenderungsgrenze_c>",
      "randbedingung_reproduziert": "<randbedingung_reproduziert>"
    },
    "name": "dachraum_messreihe_vorhang_zwei_ruecknahmeproben"
  }
}

Input Schema

NameRequiredDescriptionDefault
start_ohne_cYesVorher gemessener Wert ohne die Änderung
zurueck_ohne_cYesWert nach der beobachteten Rückkehr zum vorherigen Aufbau
zwischen_mit_cYesWert nach dem Einschalten der Beschattung
aenderungsgrenze_cYesEigene erforderliche Mindestdifferenz je Schritt
randbedingung_reproduziertYesSensorort, Zeitabstände und vergleichbare äußere Bedingungen sind festgehalten

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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. The description adds the conceptual model (a reversal test on an observed temperature movement) but does not say what the verdict looks like, how the threshold is applied, or what happens when 'randbedingung_reproduziert' is false. Some added context, but significant behavioral gaps remain.

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?

The description is short and front-loaded with the core check. However, the second sentence is a straight English translation of the first rather than new information, so half the text does not earn its place. No structural harm, but no added value from the duplication.

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 five required numeric parameters, a precondition flag, and no output schema, the description should explain what the tool returns (a verdict? a comparison result?) and how the required threshold parameter affects it. It says none of this, leaving the agent unable to predict the outcome of a call.

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 each of the five parameters is already documented in the schema. The description's before/during/after narrative loosely maps to start_ohne_c, zwischen_mit_c and zurueck_ohne_c but adds no format, unit, or interaction details beyond what the schema states. Baseline 3 is appropriate.

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 specific check ('Prüfe, ob ...') over a specific phenomenon: whether a temperature advantage seen when shading was switched on disappears again when it is reverted. The three-point before/during/after framing is clear. It does not, however, distinguish itself from the many sibling measurement-series tools, so it falls short of 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus the other Messreihe siblings (e.g. trend-knick, echte Wiederholungen, Ausreisser checks), no prerequisites beyond the schema's own precondition parameter, and no exclusions. The agent must infer applicability entirely from the scenario description.

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