Skip to main content
Glama

getecoback-climate-weather

wohnmobil_saisonwechsel_erster_getrennter_eindruck

Read-only

Ermittle, ob beim Auswintern eine dokumentierte Zwischenkontrolle vor Neueinräumen überhaupt möglich war — Find the observable window between unpacking the camper and restoring furnishings

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": {
      "bestand_entfernt_min": "<bestand_entfernt_min>",
      "erste_neue_auflage_min": "<erste_neue_auflage_min>",
      "kontrolle_min": "<kontrolle_min>",
      "gleicher_bereich": "<gleicher_bereich>"
    },
    "name": "wohnmobil_saisonwechsel_erster_getrennter_eindruck"
  }
}

Input Schema

NameRequiredDescriptionDefault
kontrolle_minYesBelegter Zeitpunkt der Sichtprüfung derselben Fläche
gleicher_bereichYesZeitpunkte und Nachweis betreffen dieselbe Fläche
bestand_entfernt_minYesMinute, in der lose gelagerte Stücke für die erste Sichtprüfung entfernt waren
erste_neue_auflage_minYesMinute, in der die erste neue Auflage die zu beurteilende Fläche wieder bedeckt

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 establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that this is a feasibility/determination question rather than a data fetch, but does not say what the verdict looks like, how the four timepoints are compared, or what happens when kontrolle_min falls outside the removable/covered window.

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 sentences with the core question front-loaded. The German and English renderings are near-duplicates, which is mild padding but does aid readability.

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 four required parameters and no output schema, the description should at least indicate the shape of the result (a verdict or window) and how the inputs combine. It signals the intent but leaves the returned value and the same-area condition's role unexplained.

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% and each parameter has a substantive description including the 0–1440 minute domain, so the schema carries the semantics. The description only loosely maps 'unpacking' and 'restoring furnishings' onto bestand_entfernt_min and erste_neue_auflage_min without adding format or edge-case meaning.

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 verb ('Ermittle'/'Find') and a precise object: whether a documented intermediate inspection between unpacking and re-furnishing was possible. The observable-window framing makes the computation concrete, though it never situates itself against the many similarly named wohnmobil siblings.

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 through the scenario clause 'beim Auswintern ... vor Neueinräumen'. There is no explicit when-to-use versus another tool, no exclusions, and no mention of what to do when a parameter (e.g., same-area evidence) is already known to fail.

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