Skip to main content
Glama

getecoback-climate-weather

warmwasser_parallelzapfung_abweichungsprobe

Read-only

Gleichzeitige Zapfung und eigene Referenzläufe getrennt auf späteres Erreichen der Wunschtemperatur prüfen — Compare simultaneous draw with individual warm-up trials.

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": {
      "a_einzeln": "<a_einzeln>",
      "b_einzeln": "<b_einzeln>",
      "a_parallel": "<a_parallel>",
      "b_parallel": "<b_parallel>",
      "bedingungen_gleich": "<bedingungen_gleich>"
    },
    "name": "warmwasser_parallelzapfung_abweichungsprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_einzelnYesSekunden bis zum Wunschwert an A im Einzellauf.
b_einzelnYesEntsprechender Einzellauf an B.
a_parallelYesSekunden bis zum Wunschwert an A bei gleichzeitiger Entnahme.
b_parallelYesEntsprechender paralleler Lauf an B.
bedingungen_gleichYesWaren vorherige Nutzungen, Zielwerte und beobachtete Zapfeinstellungen je Stelle vergleichbar?

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 establish that this is a read-only, closed-world check, and the description adds that parallel and individual runs are compared separately. It does not explain how deviations are evaluated, what happens if bedingungen_gleich is false, or how results 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 definition is a single front-loaded sentence that states the comparison and the target condition. The bilingual repetition is slightly redundant but still compact and easy to scan.

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 five-parameter analytic tool with no output schema, the description explains the comparison but not the returned result or the interpretation of the deviation probe. It also leaves the effect of the comparability flag unexplained, so an agent must infer the outcome semantics.

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 coverage is 100%, with each of the five required parameters explicitly described in the input schema. The description adds no additional meaning about those parameters beyond the comparison context.

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 specific comparison: simultaneous draw versus individual reference runs, assessed for reaching the desired temperature. It clearly identifies the operation, though it does not explicitly differentiate itself from similarly named warm-water measurement tools.

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?

It implies the tool is for cases where both parallel and individual measurements are available and comparability can be judged. It does not state when not to use it, prerequisite conditions beyond the schema, or name an alternative sibling tool.

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