Skip to main content
Glama

getecoback-raumklima

camper_standwinter_logger_zwischen_auslese_und_umzug

Read-only

Prüfe, ob ein gespeicherter Winterabschnitt beide Stellplätze enthält und daher nicht einzeln zugeordnet werden kann — Scope stored winter data across a campsite move

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": {
      "speicher_start_tag": "<speicher_start_tag>",
      "umzug_tag": "<umzug_tag>",
      "speicher_ende_tag": "<speicher_ende_tag>",
      "sensor_aufzeichnung_bestaetigt": "<sensor_aufzeichnung_bestaetigt>"
    },
    "name": "camper_standwinter_logger_zwischen_auslese_und_umzug"
  }
}

Input Schema

NameRequiredDescriptionDefault
umzug_tagYesDokumentierter Tag des Stellplatzwechsels
speicher_ende_tagYesLetzter sicher übernommener Tag im Speicher
speicher_start_tagYesErster sicher übernommener Tag im Speicher
sensor_aufzeichnung_bestaetigtYesGleiches Fahrzeug, unveränderte Sensorposition und vollständig dokumentierte Zeitbasis

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 safety is covered and the description is not required to restate it. The description does add real context by defining what the tool determines — co-presence of both pitches in one stored section — which is more than a restatement of the name. However, it says nothing about the form of the verdict (boolean vs. a scope label), and with no output schema that is a meaningful omission for a tool whose entire value is its answer.

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 a single compact sentence with the decision criterion front-loaded, which is good. The bilingual doubling is partly redundant and, because the English half frames the tool as 'scoping' rather than 'checking', it costs clarity rather than adding it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-required-parameter read-only check with a fully documented schema, the description supplies the conceptual criterion the agent needs in order to interpret a result. The remaining gap is the return value, which the description never characterizes and which no output schema covers. That is a real but limited deficiency given the annotations already establish the tool is a safe, closed-world read.

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?

All four parameters carry schema descriptions at 100% coverage, so day-window and sensor-confirmation semantics are already documented and the baseline of 3 applies. The description contributes nothing beyond that — it does not explain how speicher_start_tag, umzug_tag and speicher_ende_tag relate to each other, nor why sensor_aufzeichnung_bestaetigt gates the check.

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 German clause names a specific check and its decision criterion: whether a stored winter section contains both campsite pitches and therefore cannot be attributed individually. That is far more specific than the cryptic tool name, and it separates the tool from sibling scoping tools such as camper_stellplatzwechsel_vorher_nachher_quellenscope. The English gloss ('Scope stored winter data across a campsite move') frames it slightly differently from the German check wording, which blurs whether this asserts a condition or performs a scoping operation.

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 only implied: the phrasing 'daher nicht einzeln zugeordnet werden kann' signals the decision an agent faces when attributing stored winter data. There is no explicit when-to-use statement, no prerequisites, and no named alternative among the many campsite-move siblings. The agent must infer the situation from the scenario rather than from stated 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