Skip to main content
Glama

getecoback-raumklima

induktion_waermeverlauf_gefaess_als_versuchsfaktor

Read-only

Vergleiche bereits gemessene Zeiten zu demselben selbst definierten Beobachtungspunkt mit zwei Gefäßen, sofern das Gefäß der einzige geänderte Faktor war — Compare observed repeat timings while changing only the vessel

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": {
      "faktor_gleich": "<faktor_gleich>",
      "minuten_a1": "<minuten_a1>",
      "minuten_a2": "<minuten_a2>",
      "minuten_b1": "<minuten_b1>",
      "minuten_b2": "<minuten_b2>",
      "zeitablesung_toleranz_min": "<zeitablesung_toleranz_min>"
    },
    "name": "induktion_waermeverlauf_gefaess_als_versuchsfaktor"
  }
}

Input Schema

NameRequiredDescriptionDefault
minuten_a1YesErster beobachteter Lauf mit A
minuten_a2YesZweiter beobachteter Lauf mit A
minuten_b1YesErster beobachteter Lauf mit B
minuten_b2YesZweiter beobachteter Lauf mit B
faktor_gleichYesGleiche Kochzone, Modus und gemessene Ausgangsbedingungen einschließlich gleicher Füllmenge und desselben beobachteten Endpunkts
zeitablesung_toleranz_minYesBekannte kombinierte Unsicherheit des Vergleichs in Minuten

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, non-open-world operation, so the description does not need to explain safety. It adds useful validity context by requiring already measured times and a controlled vessel-only comparison, but it says nothing about the return value or how the comparison result should be interpreted.

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 compact and front-loads the comparison purpose and the key precondition. The German sentence is repeated almost verbatim in English, which is slightly redundant, but the overall structure is efficient.

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 six-parameter read-only comparison tool with no output schema, the description covers what is being compared and when that comparison is valid. However, it does not explain what result the caller receives, how the tolerance parameter affects the comparison, or what happens when the precondition fails.

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 six parameters are already fully documented in the input schema. The description mentions two vessels, repeat timings and the controlled-factor condition, but does not add meaning beyond the schema entries.

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 verb and resource: comparing already measured repeat timings for two vessels at the same self-defined observation point. It is clear about the controlled condition (vessel as the only changed factor), but it does not explicitly differentiate this tool from any sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The clause 'sofern das Gefäß der einzige geänderte Faktor war' gives an explicit precondition for using the tool. It does not say when not to use it or name an alternative sibling, but the intended context is clear.

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