Skip to main content
Glama

getecoback-raumklima

strommessung_woche_nutzungsmix

Read-only

Unterschiedlich häufige Alltagstypen im Wochenverbrauch getrennt hochrechnen — Weight working-day and other-day measurements by their actual weekly frequency.

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": {
      "arbeitstag_kwh": "<arbeitstag_kwh>",
      "frei_kwh": "<frei_kwh>",
      "arbeitstage": "<arbeitstage>"
    },
    "name": "strommessung_woche_nutzungsmix"
  }
}

Input Schema

NameRequiredDescriptionDefault
frei_kwhYesGemessener Tagesmittelwert für einen typischen anderen Tag, in kWh.
arbeitstageYesZahl vergleichbarer Arbeitstage in der Zielwoche, 0 bis 7.
arbeitstag_kwhYesGemessener Tagesmittelwert für einen typischen Arbeitstag, in kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description contributes the method (weighting each day type by its actual weekly frequency), which clarifies that this is a pure calculation rather than a lookup. It says nothing about the returned quantity, units, or how the weighting treats edge cases such as arbeitstage=0 or 7.

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 core statement is front-loaded and clear, but the German and English sentences are near-verbatim duplicates, so roughly half the text is redundant. Nothing is off-topic, but the bilingual restatement costs efficiency without adding information.

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 three-parameter, fully schema-documented calculation tool with no output schema, the description is adequate but thin. The main missing piece is what result the extrapolation produces and in what unit, which an agent would have to guess at for a weekly-consumption figure.

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%, so all three parameters are documented in the schema. The description adds a little meaning by framing arbeitstage as the 'actual weekly frequency' weight applied to the workday mean, but it does not explain the implied complement (the remaining days of the week as other days) or the arithmetic performed.

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 on a specific resource: extrapolating ('hochrechnen') weekly consumption by weighting workday and other-day daily averages by their weekly frequency. An agent can tell this is a computation over two day-type measurements rather than a plain measurement or error-analysis tool. It does not, however, distinguish itself from nearby siblings such as strommessung_hochrechnen or strommessung_vorhersage_praxistag.

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 usage situation is implied — you need both a workday mean and an other-day mean plus the count of workdays in the target week. There is no explicit when-to-use/when-not statement and no alternative tool is named, so selection against the many strommessung_* siblings is left to inference.

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