Skip to main content
Glama

getecoback-raumklima

wetterbericht_temperaturwert_als_messziel

Read-only

Tageswert, Stundenwert und gefühlte Außentemperatur der passenden Zimmerprüfung zuordnen — Keep apparent and daily heat data separate from timed measured-air comparisons.

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": {
      "berichtswert": "<berichtswert>",
      "raumziel": "<raumziel>",
      "zieluhrzeit_zugeordnet": "<zieluhrzeit_zugeordnet>"
    },
    "name": "wetterbericht_temperaturwert_als_messziel"
  }
}

Input Schema

NameRequiredDescriptionDefault
raumzielYesWofür wird der Wert benutzt?
berichtswertYesWas zeigt der Wetterbericht an?
zieluhrzeit_zugeordnetYesReport nennt tatsächlich die Zieluhrzeit, die für den Vergleich benötigt wird?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=false already establish that this is a safe, closed-world read, so the description is not obligated to restate safety. It adds domain behavior (values are matched to a room check, and apparent/daily heat data must not be conflated with timed measured-air values) but says nothing about what the tool returns or how an unmatched/'unbekannt' value is handled.

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-loads the assignment action before the constraint, and both sentences carry content. The abrupt switch from German to English inside a single sentence and the dash-compressed phrasing make it noticeably harder to parse than its length warrants.

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?

With three fully described required parameters and no output schema, the inputs are covered, but the description never indicates what the call produces — a classification, a decision flag, or an echoed mapping — which is the main thing an agent cannot infer. For a routing/classification-style tool this leaves a real gap.

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 coverage is 100% with German enum descriptions, so the parameters are already self-documenting; the baseline of 3 applies. The description echoes the enum values (Tageswert/Stundenwert/gefühlte) and adds a separation rule that reinforces the berichtswert distinction, but contributes no syntax, defaults, or edge-case meaning the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names concrete objects ('Tageswert, Stundenwert und gefühlte Außentemperatur') and a verb ('zuordnen'), so it is not mere tautology. But the actual operation is a classification/validation of whether a report value may serve as a comparison target, and that outcome is never stated, nor is the tool distinguished from the very large set of similarly named German sibling tools.

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 second clause ('Keep apparent and daily heat data separate from timed measured-air comparisons') implies a boundary condition for when this association is appropriate versus a timed measured-air comparison. However, it never says explicitly when to call this tool, when not to, or which sibling to use instead.

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