Skip to main content
Glama

getecoback-raumklima

raumtemperatur_dreipunkt_abflachung_folgemessung

Read-only

Wähle zwischen weiterer Beobachtung und unverändertem Messabstand nach einer abgeflachten Temperaturrate — Check whether the latest cooling segment flattened beyond a chosen tolerance

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": {
      "a_c": "<a_c>",
      "b_c": "<b_c>",
      "c_c": "<c_c>",
      "ab_min": "<ab_min>",
      "bc_min": "<bc_min>",
      "mindestdifferenz_c_h": "<mindestdifferenz_c_h>",
      "gleicher_aufbau": "<gleicher_aufbau>"
    },
    "name": "raumtemperatur_dreipunkt_abflachung_folgemessung"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_cYesTemperatur am ersten Messpunkt
b_cYesTemperatur am mittleren Messpunkt
c_cYesTemperatur am letzten Messpunkt
ab_minYesDauer des ersten Abschnitts
bc_minYesDauer des zweiten Abschnitts
gleicher_aufbauYesBeschattung, Gerätebetrieb und Messstelle in beiden Abschnitten unverändert
mindestdifferenz_c_hYesSelbst gewählte Mindestdifferenz der mittleren Raten

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the decision framing (observe further vs. keep the measurement interval) but says nothing about what the call actually returns, whether the result is a boolean or a recommendation, or how the tolerance is applied beyond the vague 'chosen tolerance'.

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?

It is short and front-loaded, but it splits into a German clause about the decision and an English clause about the check, which partially restate one another without a clear lead sentence. Nothing is wasteful, yet the bilingual mirroring costs clarity rather than earning its place.

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 seven-parameter, all-required decision tool with no output schema, the description should at least state what the result looks like or how the comparison is decided. It conveys the decision context but leaves the returned signal and the role of the uniformity precondition undocumented.

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 all seven parameters are already documented in the schema; the baseline is therefore 3. The description reinforces two of them ('latest cooling segment' implying a_c/b_c/c_c with ab_min/bc_min, and 'chosen tolerance' mapping to mindestdifferenz_c_h) but never mentions the required precondition gleicher_aufbau, which is the least self-explanatory parameter.

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 check ('Check whether the latest cooling segment flattened beyond a chosen tolerance') on a specific resource (a cooling curve's latest segment), so an agent can tell what it computes. It does not distinguish itself from the many sibling measurement/Beleg tools, and the German half frames the tool as a choice rather than a check, slightly blurring the single purpose.

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 einer abgeflachten Temperaturrate' plus 'Wähle zwischen weiterer Beobachtung und unverändertem Messabstand' implies the situation in which to call it (a rate that has already flattened). However, it names no alternative tool and gives no exclusion criteria or prerequisites, so the when-to-use picture is only implied.

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