Skip to main content
Glama

getecoback-climate-weather

haushalt_strommessgeraete_wochenrotation

Read-only

Geeignete Messgeräte für vollständige Wochenprotokolle auf mehrere Geräte verteilen — Plan how many non-overlapping batches of simultaneous household measurements are needed.

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": {
      "geraete": "<geraete>",
      "messgeraete": "<messgeraete>",
      "protokoll_tage": "<protokoll_tage>",
      "zeitbudget_tage": "<zeitbudget_tage>"
    },
    "name": "haushalt_strommessgeraete_wochenrotation"
  }
}

Input Schema

NameRequiredDescriptionDefault
geraeteYesAnzahl Haushaltsgeräte mit jeweils einem vollständigen Protokoll.
messgeraeteYesAnzahl tatsächlich geeigneter und frei verfügbarer Messgeräte.
protokoll_tageYesGleiche feste Protokolldauer je Haushaltsgerät in Tagen.
zeitbudget_tageYesGesamter verfügbarer Zeitraum in Tagen.

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?

The annotations already establish read-only and closed-world behavior, while the description adds that it plans non-overlapping simultaneous measurement batches. However, it does not state the exact return value, rounding behavior, or handling of zero devices or insufficient time budget, which is a notable gap 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?

It is a single compact sentence with no filler, and the operational goal is front-loaded. The bilingual dash construction is slightly awkward, but it does not waste space.

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 four-required-parameter calculation tool with no output schema, the description explains the planning concept but leaves the returned result and edge-case semantics underspecified. The annotations cover safety, but the agent still cannot tell exactly what will be returned.

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%, and each of the four numeric parameters is already defined in the schema: device count, meter count, protocol days, and time budget. The description alludes to the scenario but adds no format, range, or relationship details beyond the schema.

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?

It names a specific planning operation: distributing suitable measuring devices across household devices to form complete weekly protocols and computing how many non-overlapping batches are needed. This is clearly distinguishable from measurement-execution tools, though it does not name a sibling alternative.

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?

The implied use case is planning measurement rotation when several household devices need full weekly protocols but meter availability is limited. It gives no explicit when-not guidance, prerequisites, or named alternative for scheduling instead of counting batches.

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