Skip to main content
Glama

getecoback-raumklima

klima_wasserspur_betriebszeit_melden

Read-only

Zeitmarke einer vorhandenen Wasserspur mit Lauf und Abschalten vergleichen — Put a documented leak on an appliance operating timeline.

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_min": "<start_min>",
      "stopp_min": "<stopp_min>",
      "entdeckt_min": "<entdeckt_min>",
      "trockener_anfang_gesehen": "<trockener_anfang_gesehen>"
    },
    "name": "klima_wasserspur_betriebszeit_melden"
  }
}

Input Schema

NameRequiredDescriptionDefault
start_minYesStart des bereits vergangenen Laufs.
stopp_minYesEnde desselben Laufs.
entdeckt_minYesZeitpunkt der ersten Beobachtung, keine angenommene Entstehungszeit.
trockener_anfang_gesehenYesStandort unmittelbar vor diesem Lauf sichtbar trocken?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint and openWorldHint annotations already establish that this is a safe, closed-world read operation, and the description is consistent with that. The description adds that timestamps are compared against run and shutdown times, but it does not explain output, prerequisites, or how the timeline placement is computed.

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 short and front-loads the core operation before the English gloss. The bilingual translation is slightly redundant, but it remains efficient and there is little wasted wording.

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 tool with four required parameters and no output schema, the description gives only high-level context about comparing timestamps and placing a leak on a timeline. It does not explain the return value or how the reported timeline is interpreted, so the agent must rely heavily on the schema and annotations.

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 the schema descriptions already define start_min, stopp_min, entdeckt_min, and trockener_anfang_gesehen. The description does not add parameter meaning beyond what the schema provides, so the baseline of 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 identifies a concrete operation—comparing a water-trace timestamp against run and shutdown times and placing a documented leak on an appliance timeline—but the wording is cryptic. The tool name says 'melden' (report) while the description says 'compare/put', so the exact action must be inferred. It also does not explicitly differentiate this from the many sibling klima 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?

Usage is only implied by the mention of a documented leak and operating timeline. There is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative among the sibling 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