Skip to main content
Glama

getecoback-raumklima

heizverbrauch_lueftungsereignis_zeitfolge

Read-only

Ein Heizsignal als vor, nach oder zeitlich nicht eindeutig zu einem Lüftungsereignis einordnen — Check whether time uncertainty permits temporal attribution of a heating response.

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": {
      "lueften_ab_min": "<lueften_ab_min>",
      "lueften_bis_min": "<lueften_bis_min>",
      "heizsignal_ab_min": "<heizsignal_ab_min>",
      "heizsignal_bis_min": "<heizsignal_bis_min>"
    },
    "name": "heizverbrauch_lueftungsereignis_zeitfolge"
  }
}

Input Schema

NameRequiredDescriptionDefault
lueften_ab_minYesFrühestmöglicher Lüftungsbeginn auf gemeinsamer Uhr.
lueften_bis_minYesSpätestmöglicher Lüftungsbeginn auf derselben Uhr.
heizsignal_ab_minYesFrühestmöglicher Beginn des beobachteten Heizsignals.
heizsignal_bis_minYesSpätestmöglicher Beginn des beobachteten Heizsignals.

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?

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully adds that the outcome is a three-way classification (before / after / not temporally determinable), which is real behavioral context. It does not, however, explain how overlapping or zero-width intervals are resolved, nor what the returned value actually looks like — relevant because there is no output schema.

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 compact sentence pair, front-loaded with the operation and its outcome. The German and English render the same content, which is mild duplication rather than padding, so it stays 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?

Four required parameters, no output schema, and a purely computational result: the description should say what the result is shaped like (e.g., a category or a boolean plus reason) and how the two interval pairs are compared. It states the classification categories but leaves the return shape and tie-breaking logic unstated.

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 itself already states that all four values are earliest/latest bounds on a shared clock. The description adds no syntax, unit, or interpretation guidance beyond that, so the baseline 3 for schema-covered parameters applies.

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 names a specific operation (classify a heating signal as before, after, or temporally ambiguous relative to a ventilation event) with a clear resource and predicate, so an agent can tell what it computes. It falls short of 5 only because the German/English doubling is compressed and the 'Zeitfolge' framing does not explicitly contrast with any sibling ordering/attribution tool.

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 phrase 'Check whether time uncertainty permits temporal attribution' implies the motivating condition, but there is no explicit statement of when to call this versus other sequence/attribution tools and no stated preconditions or exclusions. The agent must infer the use case from the name and the four interval parameters.

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