Skip to main content
Glama

getecoback-climate-weather

terrassenbeschattung_zimmerprobe_mit_referenzraum

Read-only

Beobachtete Innenraumänderung bei Außenbeschattung gegen einen unveränderten Referenzraum einordnen — Compare changes in two rooms without attributing the difference automatically.

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_vorher_c": "<a_vorher_c>",
      "a_nachher_c": "<a_nachher_c>",
      "b_vorher_c": "<b_vorher_c>",
      "b_nachher_c": "<b_nachher_c>",
      "zeit_und_nutzung_aehnlich": "<zeit_und_nutzung_aehnlich>"
    },
    "name": "terrassenbeschattung_zimmerprobe_mit_referenzraum"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_vorher_cYesTemperatur im Raum mit neu beobachtetem Außenschatten vor dem Vergleich.
b_vorher_cYesTemperatur im zeitgleich beobachteten unveränderten Raum am Start.
a_nachher_cYesDessen Temperatur nach dem dokumentierten Abschnitt.
b_nachher_cYesTemperatur im unveränderten Vergleichsraum am Ende.
zeit_und_nutzung_aehnlichYesZeitfenster, Lüftung und sonstige wesentliche Wärmequellen vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/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. Beyond that, the description adds genuine semantic context: the result is an interpretive classification ('einordnen') and must not be read as automatic causal attribution of the difference to the shading — a real caveat for how the agent should treat the result.

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?

Two short clauses, front-loaded with the subject ('Beobachtete Innenraumänderung bei Außenbeschattung') followed by the caveat. The bilingual rendering is mildly redundant, but nothing is padding and the key constraint is placed where it will be read.

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?

A read-only tool with five required parameters and no output schema needs only modest explanation, which this largely provides. What is missing is how the result is shaped and, importantly, what happens when zeit_und_nutzung_aehnlich is false — whether the tool still compares or refuses.

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% and every parameter, including the a/b role split and the comparability boolean, is already documented in the schema itself. The description restates the A-with-shading vs. B-unchanged framing but adds no new detail about units, ranges, or how the boolean gates the result, so the baseline of 3 applies.

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 operation ('Beobachtete Innenraumänderung ... gegen einen unveränderten Referenzraum einordnen') and specifies both the stimulus (Außenbeschattung) and the control (unveränderter Referenzraum). It is clearly a two-room temperature comparison rather than a single-room reading, but it never distinguishes itself from look-alike siblings such as feuchte_versuch_referenzraum or arbeitsplatz_ersatzraum_ruhe_waerme_vergleich.

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?

Usage is implied rather than stated: the agent can infer this applies when a new exterior shading has been installed in one room while a comparable room was left alone. The clause 'without attributing the difference automatically' gives a useful interpretive constraint, but there is no explicit when-not guidance, no mention of what to do if comparability fails, and no named alternative tool.

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