Skip to main content
Glama

getecoback-climate-weather

camper_staufach_winter_nachbesuch_neu_abgedeckt

Read-only

Berechne, wie viele tatsächlich neue Stauraumpunkte der zweite Winterbesuch abgedeckt hat — Deduplicate two inspections of camper storage points

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": {
      "auf_plan": "<auf_plan>",
      "erstbesuch": "<erstbesuch>",
      "zweitbesuch": "<zweitbesuch>",
      "gemeinsam": "<gemeinsam>",
      "plan_unveraendert": "<plan_unveraendert>"
    },
    "name": "camper_staufach_winter_nachbesuch_neu_abgedeckt"
  }
}

Input Schema

NameRequiredDescriptionDefault
auf_planYesAnzahl eindeutiger Stauraumpunkte auf dem eigenen Plan
gemeinsamYesDieselben markierten Punkte mit Befund an beiden Besuchen
erstbesuchYesPunkte mit vollständigem Sichtbefund beim ersten Besuch
zweitbesuchYesPunkte mit vollständigem Sichtbefund beim zweiten Besuch
plan_unveraendertYesDie Fahrzeugbereiche wurden zwischen den Besuchen gleich bezeichnet und nicht umgebaut

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?

readOnlyHint=true and openWorldHint=false already tell the agent this is a safe, closed-world computation, so the bar is lower. The description adds the deduplication intent, but leaves open what happens when plan_unveraendert is false — whether the tool errors, returns zero, or gives a partial result is undisclosed, which is meaningful behavior for this calculation.

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 compact clauses with the computed quantity front-loaded and the English gloss following as clarification. No filler, though the German/English mix is slightly redundant rather than additive.

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?

For a five-required-parameter read-only computation with no output schema, the description states what is computed (a count of new storage points) but not the return shape nor the error/edge behavior tied to plan_unveraendert. Adequate but with a clear gap an agent would notice before calling.

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%, with each of the five parameters documented in the schema itself, so the baseline is 3. The description adds only the general notion of deduplicating two inspections; it does not explain how erstbesuch/zweitbesuch relate to gemeinsam or what plan_unveraendert changes about the computation.

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 ("Berechne") and a precise resource ("tatsächlich neue Stauraumpunkte der zweite Winterbesuch"), plus a clarifying gloss ("Deduplicate two inspections of camper storage points"). It is clear what the tool computes, but it does not distinguish itself from the numerous sibling tools about camper visits (e.g. nachwinter_befund_neu_oder_wiederholt), leaving the agent to infer the boundary.

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 phrase "Deduplicate two inspections" implies the situation in which it applies (comparing a first and second visit), so usage is inferable. However, there is no explicit when-to-use statement, no exclusion, and no named alternative for closely related sibling tools.

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