Skip to main content
Glama

getecoback-raumklima

warmwasser_nutzungsfolge_festtermine_tausch

Read-only

Zwei bereits beobachtete Reihenfolgen für verschiedene Warmwassernutzungen gegen feste Termine prüfen — Fit two measured use orders to actual household deadlines.

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": "<start>",
      "a_frist": "<a_frist>",
      "b_frist": "<b_frist>",
      "a_dauer": "<a_dauer>",
      "b_dauer": "<b_dauer>",
      "pause_a_b": "<pause_a_b>",
      "pause_b_a": "<pause_b_a>",
      "beide_proben_passend": "<beide_proben_passend>"
    },
    "name": "warmwasser_nutzungsfolge_festtermine_tausch"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYesFrühester Start, Minuten seit Mitternacht.
a_dauerYesDauer von A ohne Pause.
a_fristYesSpätestes Ende der Nutzung A.
b_dauerYesDauer von B ohne Pause.
b_fristYesSpätestes Ende der Nutzung B.
pause_a_bYesBei dieser A–B-Folge beobachteter brauchbarer Abstand.
pause_b_aYesBei der umgekehrten Folge beobachteter brauchbarer Abstand.
beide_proben_passendYesWurden beide Folgen bei vergleichbarem Ausgangszustand vollständig beobachtet?

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the sequences must already be measured/observed, but it does not explain the return result or how failed deadline fits are reported.

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?

The description is a single compact bilingual sentence that front-loads the operation and resource without filler. The German–English duplication is slightly redundant but not wasteful for a bilingual tool.

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?

All eight required parameters are fully described in the schema, reducing the description's burden. However, there is no output schema and the description does not explain what the check returns—such as which sequence fits or what a failed fit looks like—leaving a meaningful gap for an 8-parameter tool.

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 the schema already documents all eight parameters in detail. The description adds only broad context (measured use orders, actual household deadlines) and does not deepen parameter meaning beyond what the schema provides, making the baseline 3 appropriate.

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 operation (prüfen/fit) on a specific resource (two already observed Warmwassernutzungs-Reihenfolgen) against fixed household deadlines. It is clear what the tool computes, though it does not explicitly distinguish itself from the many sibling warm-water tools.

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?

The description gives no when-to-use or when-not-to-use guidance and does not name alternatives. An agent can infer that this tool checks two observed sequences against deadlines, but nothing helps it choose this tool over the neighboring warm-water 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