Skip to main content
Glama

getecoback-raumklima

camper_granulat_zwei_besuche_saettigungsintervall

Read-only

Grenze für zwei Zonen ein, wann eine belegte Auffanggrenze zwischen Besuchen erreicht wurde — Bound when winter reservoir limits were reached between 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": {
      "erster_tag": "<erster_tag>",
      "zweiter_tag": "<zweiter_tag>",
      "wohnraum": "<wohnraum>",
      "heck": "<heck>",
      "kontinuierliche_boxzuordnung": "<kontinuierliche_boxzuordnung>"
    },
    "name": "camper_granulat_zwei_besuche_saettigungsintervall"
  }
}

Input Schema

NameRequiredDescriptionDefault
heckYesHeckstauraum beim späteren Besuch
wohnraumYesWohnraum beim späteren Besuch
erster_tagYesFrüherer Besuch, an dem beide Boxen nachweislich unter ihrer Hersteller-Kontrollmarkierung lagen
zweiter_tagYesTag des späteren Besuchs
kontinuierliche_boxzuordnungYesIdentische Boxen ohne dokumentierte Entleerung oder Austausch in denselben Zonen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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 the safety profile is covered. The description adds almost nothing beyond that: it does not say what the returned 'bound' looks like, what happens when the boxes were not provably below the mark, or how the interval is derived. For a computation tool with no output schema this leaves real behavioral gaps.

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?

The description is short, but it duplicates the same content in German and English without the English version adding precision. The key concept ('Grenze') is buried in dense compound nouns rather than front-loaded as a plain statement of what is returned.

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?

This is a non-trivial five-parameter computation with an implicit interval result and no output schema, yet the description never states what the tool returns or what the edge cases (e.g. 'nicht_abgelesen') yield. Given the tool's complexity, the definition is too thin to call it correctly with confidence.

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 fully documented in German (day range 0–730, enum meaning for heck/wohnraum, the continuous box-assignment condition). The description adds no parameter meaning beyond what the schema already provides, so the baseline 3 applies.

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 does name a verb ('Grenze ... ein' / 'Bound') and a resource (winter reservoir limits reached between visits for two zones), so the general intent is inferable. However, the phrasing 'belegte Auffanggrenze' and 'Sättigungsintervall' is opaque jargon, and nothing distinguishes it from the many sibling camper tools. An agent can guess it relates to saturation between two visits but cannot confidently state what it computes.

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 when-to-use guidance, no when-not-to-use, and no named alternative among the numerous sibling tools. The description implicitly suggests it applies to two-visit comparisons, but the agent must infer the triggering conditions entirely from the parameter names.

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