Skip to main content
Glama

getecoback-raumklima

camper_standkontrollen_nach_hintereinander_ausfall

Read-only

Ermittle die längste tatsächlich offene Pause zwischen protokollierten Winterbesuchen — Find the longest unobserved interval between completed winter visits

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": {
      "start_tag": "<start_tag>",
      "besuch_a_tag": "<besuch_a_tag>",
      "besuch_b_tag": "<besuch_b_tag>",
      "auswertungstag": "<auswertungstag>",
      "intervallgrenze_tage": "<intervallgrenze_tage>"
    },
    "name": "camper_standkontrollen_nach_hintereinander_ausfall"
  }
}

Input Schema

NameRequiredDescriptionDefault
start_tagYesTag der vollständigen ersten Winterbegehung
besuch_a_tagYesErster späterer belegter Besuch
besuch_b_tagYesZweiter späterer belegter Besuch, bei fehlendem zweitem Besuch wie A
auswertungstagYesTag der Auswertung
intervallgrenze_tageYesPersönlich gesetzte längste akzeptierte Beobachtungslücke

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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 need not repeat it. What remains undisclosed is behavior that matters here: what happens when the computed gap exceeds intervallgrenze_tage (truncation, null, or error), how ties or a missing second visit are handled, and whether the result is a duration or the interval endpoints. Since no output schema exists, this is a real gap.

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 front-loaded sentence with the key qualifier ('tatsächlich offene') placed before the resource. The German/English duplication is redundant for a bilingual audience that only needs one, but it costs little and adds no confusion.

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

Completeness2/5

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

Five required numeric parameters with cryptic domain roles, no output schema, and a comparison against a user-set threshold — this tool needs more than one sentence. The description never explains what is returned or how the threshold parameter affects the response, leaving the agent to guess at the most consequential behavior.

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 all five numeric parameters carry their own explanations, which sets the baseline at 3. The description adds nothing about how start_tag, besuch_a_tag, besuch_b_tag and auswertungstag interact, nor how intervallgrenze_tage constrains the result beyond the schema's own wording.

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 states a specific computed quantity: the longest genuinely unobserved gap between logged winter visits. The qualifier 'tatsächlich offene' / 'unobserved' distinguishes it from a naive max-difference calculation. It does not, however, differentiate itself from near-neighbours such as camper_absorber_rueckkehr_vor_offener_besuchspause or camper_granulat_zwei_besuche_saettigungsintervall, so an agent must 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 Guidelines2/5

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

There is no when-to-use guidance, no preconditions (e.g. that the visits must be chronologically ordered), and no pointer to any alternative tool. The agent is told what is computed but not in which situation this tool is the right choice.

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