Skip to main content
Glama

getecoback-climate-weather

gefrierfach_nach_abtaukontrolle_energieabschnitte

Read-only

Einen dokumentierten Wiederanlauf nach vollständiger Pflege aus einem mehrtägigen Vergleich gesondert ausweisen — Separate a noted freezer restart block from routine energy observation.

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": {
      "gesamt_kwh": "<gesamt_kwh>",
      "gesamt_h": "<gesamt_h>",
      "wiederanlauf_kwh": "<wiederanlauf_kwh>",
      "wiederanlauf_h": "<wiederanlauf_h>"
    },
    "name": "gefrierfach_nach_abtaukontrolle_energieabschnitte"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamt_hYesGesamtlänge desselben Protokolls in Stunden.
gesamt_kwhYesErfasste Energie des gesamten Protokolls.
wiederanlauf_hYesGemessene Dauer genau dieser Phase in Stunden.
wiederanlauf_kwhYesDarin gemessene Energie einer getrennt protokollierten Wiederanlaufphase.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a read-only reporting operation. Beyond that, the description adds little behavioral context: it does not explain what is returned, how the restart block is identified, or any assumptions about the input measurements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the action, but it redundantly states the same idea in German and English without adding precision. Every sentence should earn its place, and here the bilingual duplication consumes space without clarifying the operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has four required numeric parameters and no output schema. Because there is no output schema, the description should explain what gets returned—for example, whether it returns separated energy segments, ratios, or a report—but it does not. Given the numeric comparison implied by the inputs, the description is too vague to be complete.

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 all four parameters (gesamt_kwh, gesamt_h, wiederanlauf_kwh, wiederanlauf_h) are already documented in the schema. The description adds no additional meaning about their units, relationships, or how the restart segment must fit within the total protocol, so the baseline of 3 is appropriate.

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 does state a purpose—separating a documented restart block from routine energy observation—but it is abstract and bilingual, and it never clearly explains what 'gesondert ausweisen' means operationally. It does not distinguish itself from any sibling tool, so an agent cannot confidently tell when this is the right tool versus another gefrierfach or energy-observation sibling.

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?

There is no explicit when-to-use or when-not-to-use guidance. The phrase 'nach vollständiger Pflege' hints at a precondition, but the description does not say what qualifies as a documented restart, when routine observation should be used instead, or whether this is meant only for multi-day comparisons.

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