Skip to main content
Glama

getecoback-raumklima

raumkuehlung_uebergabe_thermometer_belastungspaar

Read-only

Vergleiche beim Raumwechsel nur geloggte Temperaturänderungen mit ähnlichem Innen-Außen-Abstand am Start — Compare logged cooling changes only within a matched starting temperature context

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": {
      "innen_a_start_c": "<innen_a_start_c>",
      "aussen_a_start_c": "<aussen_a_start_c>",
      "innen_a_ende_c": "<innen_a_ende_c>",
      "innen_b_start_c": "<innen_b_start_c>",
      "aussen_b_start_c": "<aussen_b_start_c>",
      "innen_b_ende_c": "<innen_b_ende_c>",
      "toleranz_c": "<toleranz_c>",
      "modus_dauer_und_licht_vergleichbar": "<modus_dauer_und_licht_vergleichbar>"
    },
    "name": "raumkuehlung_uebergabe_thermometer_belastungspaar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toleranz_cYesGewählte Toleranz des Start-Temperaturabstands in °C
innen_a_ende_cYesInnenwert am Ende desselben Messfensters in Raum A
innen_b_ende_cYesInnenwert am Ende in Raum B
innen_a_start_cYesInnenwert am Start in Raum A
innen_b_start_cYesInnenwert am Start in Raum B
aussen_a_start_cYesAußenwert gleichzeitig zu Raum A
aussen_b_start_cYesAußenwert gleichzeitig zu Raum B
modus_dauer_und_licht_vergleichbarYesMessdauer, Gerätemodus und Sonneneintrag waren ähnlich dokumentiert

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the important constraint that only logged changes are compared and only within a matched starting temperature context, but it does not say what happens when no match exists or how the returned comparison is presented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with no padding, and it places the comparison restriction before the explanatory rewrite. The bilingual restatement is redundant but does not obscure the core instruction.

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 complex eight-parameter comparison with no output schema, the description gives the core matching idea but omits the return value and how a comparison is reported. The schema supplies parameter details and annotations cover safety, but there is still a gap around output expectations.

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 eight parameters already carry their own meanings. The description adds the conceptual link between 'ähnlichem Innen-Außen-Abstand am Start' and the matching/tolerance logic, but it does not explain the A/B pair structure or the boolean comparability flag beyond 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 has a specific verb 'Vergleiche' and resource 'geloggte Temperaturänderungen', with the scope limited to room changes where the starting indoor-outdoor difference is similar. It is clear what the tool does, but it does not explicitly distinguish it from other comparison or handover tools by name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The phrase 'beim Raumwechsel nur geloggte Temperaturänderungen' sets a clear condition: use it when comparing logged changes during a room switch, and only under matched starting indoor-outdoor conditions. It does not name an alternative tool or state a when-not-to-use case, so it falls short of full routing guidance.

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