Skip to main content
Glama

getecoback-climate-weather

stromjournal_umstellung_uebergangszeit_ausgrenzen

Read-only

Eine dokumentierte Übergangsphase beim Nutzungswechsel vom Vorher-Nachher-Vergleich abtrennen — Exclude the transition period from a before/after consumption comparison.

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": {
      "vor_tage": "<vor_tage>",
      "vor_kwh": "<vor_kwh>",
      "uebergang_tage": "<uebergang_tage>",
      "uebergang_kwh": "<uebergang_kwh>",
      "nach_tage": "<nach_tage>",
      "nach_kwh": "<nach_kwh>",
      "aufgabe_gleich": "<aufgabe_gleich>"
    },
    "name": "stromjournal_umstellung_uebergangszeit_ausgrenzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
vor_kwhYesGemessener Verbrauch der vollständigen Tage vor der Änderung.
nach_kwhYesGemessener Verbrauch unter dem neuen Nutzungsablauf.
vor_tageYesVollständige Tage vor der Änderung.
nach_tageYesVollständige Tage unter dem neuen Nutzungsablauf.
uebergang_kwhYesVerbrauch ausschließlich der Übergangstage.
aufgabe_gleichYesGleiche erfasste Geräte und vergleichbare Haushaltsaufgabe?
uebergang_tageYesSeparat dokumentierte Übergangstage.

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 that this is a read-only, closed-world operation, so the description does not need to explain safety. It adds the behavioral idea of excluding transition data from comparison, but does not explain the calculation result, assumptions, or what happens when the task comparability flag is false.

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 a single front-loaded sentence with the core action stated first. The German/English duplication adds some redundancy, but it remains efficient and easy to parse.

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 seven-parameter calculation tool with no output schema, the description is somewhat thin: it does not describe the returned comparison or clarify how the transition exclusion affects the result. The fully documented input schema compensates for much of this, but the behavioral picture remains incomplete.

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 seven parameters are already documented in the input schema. The description adds only the high-level concept of the transition period and does not give extra meaning, examples, or constraints 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?

The description names a specific action (exclude/abtrennen) and resource (the documented transition period in a before/after consumption comparison). It is clear what the tool does, but it does not distinguish it from any alternative tool or sibling behavior.

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 description implies the usage scenario: when a usage change includes a documented transition phase that should not pollute the before/after comparison. It does not state when not to use the tool, prerequisites such as comparable household tasks, or any alternative approach.

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