Skip to main content
Glama

getecoback-climate-weather

camper_winter_sichtkontrolle_zone_einmessfenster

Read-only

Prüfe, ob alle zugänglichen Innenzonen während desselben Besuchs für die Übergabe erfasst wurden — Check whether three inspection zones belong to the same camper visit

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": {
      "besuch_ab_min": "<besuch_ab_min>",
      "besuch_bis_min": "<besuch_bis_min>",
      "rahmen_min": "<rahmen_min>",
      "polster_min": "<polster_min>",
      "stauraum_min": "<stauraum_min>",
      "ortsmarken_eindeutig": "<ortsmarken_eindeutig>"
    },
    "name": "camper_winter_sichtkontrolle_zone_einmessfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
rahmen_minYesZeit der aufgenommenen Rahmenbeobachtung
polster_minYesZeit der aufgenommenen Polsterbeobachtung
stauraum_minYesZeit der aufgenommenen Staufachbeobachtung
besuch_ab_minYesBesuchsfenster ab gemeinsamer Tageszeit
besuch_bis_minYesEnde desselben Besuchs
ortsmarken_eindeutigYesAlle Aufzeichnungen zeigen die richtige Stelle desselben Fahrzeugs

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is already covered and the description need not repeat it. The description does add a meaningful framing — that the tool tests the same-visit grouping of three zones — but says nothing about the outcome semantics (what a failed check means, whether a visit window is inclusive, what happens when ortsmarken_eindeutig is false).

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?

A single compact sentence pair, front-loaded with the German statement of intent and an English gloss. The bilingual duplication is slightly redundant but genuinely useful for an agent matching terms to the German parameter names.

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?

No output schema exists, so the description should ideally explain what the check returns (pass/fail, mismatched zones), and it does not. With six required parameters and a non-obvious validation logic, the definition is adequate to start but leaves the agent guessing at the result semantics and at how the visit window interacts with the zone timestamps.

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%, so every one of the six parameters already carries its own description; the baseline of 3 applies. The description names the three zones and the 'same visit' notion, which loosely ties besuch_ab_min/besuch_bis_min to zone times, but it adds no clarification of the 0–1440 minute window, boundary inclusivity, or the role of ortsmarken_eindeutig as a gate.

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 states the intent in two languages: check whether the three inspection zones (Rahmen, Polster, Stauraum) were recorded during the same camper visit. The verb+resource is present but vague — 'Prüfe, ob ... erfasst wurden' — and it never names the comparison against a visit window or the ortsmarken check. Sibling names are so opaque that differentiation is largely left to the schema parameter names.

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 explicit statement of when to call this versus any sibling. The 'während desselben Besuchs' phrasing implies a same-visit consistency check, but no prerequisites, no exclusions, and no mention of what to do when the check fails or which sibling handles re-recording.

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