Skip to main content
Glama

getecoback-raumklima

sommerlueften_temperaturfenster

Read-only

Mit Innen- und Außenmessung samt Gerätegenauigkeit prüfen, ob Lüften jetzt fühlbar kühlen kann — Check whether outdoor air is reliably cooler right now.

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_c": "<innen_c>",
      "aussen_c": "<aussen_c>",
      "genauigkeit_innen_c": "<genauigkeit_innen_c>",
      "genauigkeit_aussen_c": "<genauigkeit_aussen_c>"
    },
    "name": "sommerlueften_temperaturfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
innen_cYesSchattenmessung innen in °C.
aussen_cYesSchattenmessung draußen in °C.
genauigkeit_innen_cYesAbsoluter Fehler laut Innenthermometer in °C.
genauigkeit_aussen_cYesAbsoluter Fehler laut Außenthermometer in °C.

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?

Annotations already declare this is a non-destructive, closed-world read, so the safety profile is covered. The description does add the important behavioral point that the check is a reliability judgement ('reliably cooler') rather than a raw comparison, which explains why the two accuracy figures are required. It does not disclose what the operation returns or how the reliability margin is formed, which matters since there is no output schema.

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?

The definition is a single front-loaded sentence pair with the decision goal stated immediately. The same content is delivered twice (German then English), which is mild redundancy, but nothing else is wasted.

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?

For a four-required-parameter advisory computation with no output schema, the description never indicates what the answer looks like or how to interpret it (a verdict, a margin, a recommended action). Combined with the absence of usage conditions, an agent knows what to feed in but not what it will get back or when the tool is the right one to 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% and each parameter already states units, ranges and that readings are shade measurements, so the schema carries the burden. The description adds only the semantic link that the accuracy inputs exist to make the cooling verdict 'reliable', without giving tolerance thresholds or how the four values combine. 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 concrete verb and decision ('prüfen, ob Lüften jetzt fühlbar kühlen kann' / 'Check whether outdoor air is reliably cooler right now') and makes clear the inputs are indoor and outdoor readings plus their device accuracy. That is specific enough that an agent can distinguish this comparison tool from generic sensor helpers, though it never names a sibling to differentiate against.

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 word 'jetzt' / 'right now' implies a point-in-time decision use case, and the framing as a cooling-feasibility check gives an implied context for calling it. However, there is no explicit when-to-use vs when-not guidance, no note on how it relates to forecasting or device-selection siblings, and no stated prerequisites beyond the parameters.

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