Skip to main content
Glama

getecoback-raumklima

bad_erholung_duschfolge_wann_nachprobe_startet

Read-only

Kläre, bei welcher von zwei Duschfolgen eine vollständige Erholungsprobe vor der nächsten Nutzung möglich war — Identify which shower sequence allows an uncontaminated recovery observation

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": {
      "abstand_a_min": "<abstand_a_min>",
      "abstand_b_min": "<abstand_b_min>",
      "noetige_probedauer_min": "<noetige_probedauer_min>",
      "beobachtung_bis_naechste_nutzung": "<beobachtung_bis_naechste_nutzung>"
    },
    "name": "bad_erholung_duschfolge_wann_nachprobe_startet"
  }
}

Input Schema

NameRequiredDescriptionDefault
abstand_a_minYesZeit vom Ende der ersten Dusche bis zur nächsten Nutzung in Folge A
abstand_b_minYesEntsprechender Abstand in Folge B
noetige_probedauer_minYesEigenes vorab festgelegtes Erholungs-Messfenster
beobachtung_bis_naechste_nutzungYesDuschende und neue Feuchtequelle sind in beiden Fällen sicher protokolliert

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds the decision framing but discloses nothing about the actual outcome — no output shape, no tie-breaking when both or neither sequence qualifies, and no explanation of how 'beobachtung_bis_naechste_nutzung' gates the verdict. For a pure computation with no output schema, the decision rule should be spelled out.

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 that states the question to be resolved, with no filler. The German/English duplication conveys nothing new on the second pass, which keeps it from a 5.

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?

Parameters are fully documented and the tool is a read-only computation, so the basics are covered. However, with no output schema the description is the only place the return value and the tie/edge-case behavior could be described, and it omits both — an agent cannot tell what it receives back or how the boolean flag changes the answer.

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% and all four parameters carry German descriptions, so the schema does the heavy lifting and baseline 3 applies. The prose adds no format, unit, or interaction detail beyond the schema — notably it never clarifies why the boolean observation flag is required rather than optional.

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 gives a concrete verb ('Kläre' / 'Identify') and a concrete resource: which of two shower sequences admits a full recovery-probe window before the next use. That is specific enough for an agent to grasp the operation without opening the schema. It stops short of 5 because it never names the close-sounding siblings (e.g. warmwasser_erholung_zwei_gepruefte_pausen, bad_feuchte_erholung_protokoll) that an agent would have to choose between.

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?

Usage is only implied by the framing of the decision question — the agent can infer it is for comparing exactly two sequences and picking one. There is no explicit when-to-use, no prerequisites, and no statement of when a sibling would be the better call. The bilingual restatement adds no guidance.

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