Skip to main content
Glama

getecoback-climate-weather

camper_tiefster_messwert_klimadaten_kaltperiode

Read-only

Trenne die Temperatur am Besuchstag vom gespeicherten Minimum der stillgelegten Fahrzeugzone — Interpret a winter minimum separately from the visit temperature

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": {
      "tiefstwert_c": "<tiefstwert_c>",
      "besuch_c": "<besuch_c>",
      "modell_untergrenze_c": "<modell_untergrenze_c>",
      "speicher_seit_stilllegung_belegt": "<speicher_seit_stilllegung_belegt>"
    },
    "name": "camper_tiefster_messwert_klimadaten_kaltperiode"
  }
}

Input Schema

NameRequiredDescriptionDefault
besuch_cYesAktuelle Temperatur am gleichen Sensor
tiefstwert_cYesAbgelesenes Minimum des Winterspeichers in einer Fahrzeugzone
modell_untergrenze_cYesLaut genauer Geräteunterlage untere Grenze für den betrachteten Betrieb
speicher_seit_stilllegung_belegtYesSensor blieb in der betrachteten Zone und der Speicher deckt den gesamten betrachteten Abschnitt ab

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description contributes the domain caveat that a stored minimum from a decommissioned zone must be interpreted separately from the visit temperature, which is genuinely beyond the annotations, but it says nothing about what happens to the two numeric inputs or how the boolean coverage flag affects 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 distinguishing operation. The English half is essentially a translation of the German half rather than new information, which is mild redundancy but not bloat.

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?

All four required parameters are covered and the read-only nature is declared via annotations, so the call itself is executable. With no output schema, the description should have said what is returned, and it leaves the role of modell_untergrenze_c and the coverage flag uninterpreted.

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 every one of the four required parameters is already documented in the schema, making 3 the baseline. The description adds the conceptual framing of the besuch_c versus tiefstwert_c split but no format, range, or interpretation detail beyond the schema text.

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?

"Trenne die Temperatur am Besuchstag vom gespeicherten Minimum" names a verb and the two quantities being separated, so the conceptual aim is graspable. However, it never says what the tool actually produces (a corrected value, a verdict, a difference?), and it draws no boundary against the many camper_* sibling tools that also compare stored versus observed readings.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus an alternative, no prerequisites, and no exclusion. The description is a statement of intent (don't conflate a decommissioned zone's stored winter minimum with the visit-day temperature), not usage guidance for an agent.

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