Skip to main content
Glama

getecoback-climate-weather

heizwaesche_endpunkt_zwischen_zwei_stichproben

Read-only

Den tatsächlichen Zielzeitpunkt zwischen belegten Nass- und Trockenbeobachtungen eingrenzen — Find the bounded window in which a verified textile target was first observed.

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": {
      "miteinander_vergleichbar": "<miteinander_vergleichbar>",
      "letzter_negativ_min": "<letzter_negativ_min>",
      "erste_passend_min": "<erste_passend_min>",
      "schaltzeit_min": "<schaltzeit_min>"
    },
    "name": "heizwaesche_endpunkt_zwischen_zwei_stichproben"
  }
}

Input Schema

NameRequiredDescriptionDefault
schaltzeit_minYesTatsächlich beobachtete Abschaltzeit in derselben Tagesachse.
erste_passend_minYesTagesminute der ersten nachfolgenden Probe, die das Ziel tatsächlich bestätigte.
letzter_negativ_minYesTagesminute der letzten Probe, die das Trockenziel klar verfehlte.
miteinander_vergleichbarYesWaren die zuverlässig zugeordneten Stichproben ohne zwischenzeitliche Neunutzung derselben Ladung vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/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 correctly implies a pure computation. However, it does not disclose the important conditional behavior tied to 'miteinander_vergleichbar' — what happens when the samples are not comparable (error, null, or a widened window) is left entirely implicit. No output schema exists, yet the returned window's shape is only vaguely gestured at.

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 clauses, German then English translation, front-loaded with the action. The bilingual duplication is mild redundancy but functional for disambiguation and nothing is wasted.

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 read-only computation with 4 required numeric parameters and no output schema, the description should at least characterize the returned window or the incomparability branch. It conveys the general intent but leaves the result format and failure mode unspecified, so it is adequate rather than complete.

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 four parameters, including the 0–1440 minute bounds, are already fully documented in the schema. The description adds only the framing that the two sample parameters bracket a target, which is a modest semantic gain over the schema baseline.

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 uses a specific verb ('eingrenzen' / 'find the bounded window') on a specific object ('tatsächlichen Zielzeitpunkt' / 'verified textile target') and frames the inputs as bracketing wet/dry observations. This is clear enough to distinguish it from pure measurement or removal tools, but it never names a sibling, and the near-identical sibling names (e.g. 'heizwaesche_verbrauch_am_trockenziel_eingrenzen') mean the agent still has to infer the difference.

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 or when-not-to-use guidance, no mention of prerequisites (e.g. that two comparable samples must already exist), and no reference to any alternative tool. The agent must infer the call condition entirely from the purpose phrase.

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