Skip to main content
Glama

getecoback-raumklima

haushaltsstrom_vereinbarte_spitzenbeobachtung

Read-only

Bei drei bestätigten Haushaltsaufgaben die beobachtete gemeinsame Leistung gegen ein selbst gewähltes Messbudget prüfen — Check measured simultaneous draw against a voluntary household budget.

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": {
      "ab_zusammen_w": "<ab_zusammen_w>",
      "ac_zusammen_w": "<ac_zusammen_w>",
      "haushaltsziel_w": "<haushaltsziel_w>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "haushaltsstrom_vereinbarte_spitzenbeobachtung"
  }
}

Input Schema

NameRequiredDescriptionDefault
vergleichbarYesBeide Messungen nutzen übereinstimmende Messgrenze und dokumentierte Einsatzzustände.
ab_zusammen_wYesGleichzeitig auf dem gemeinsamen Messgerät beobachtete Gesamtleistung für die freigegebene Kombination A und B.
ac_zusammen_wYesVergleichbar beobachtete Gesamtleistung der bereits freigegebenen Kombination A und C.
haushaltsziel_wYesFreiwilliger Schwellenwert zur Koordination, ohne Aussage zur elektrischen Auslegung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, matching the 'prüfen' (check) framing, so no contradiction. The description adds one genuinely useful behavioral note: the budget is self-chosen and coordination-oriented rather than an electrical-design statement. It does not disclose the return shape or what a failing/at-threshold result looks like.

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 with the precondition front-loaded, followed by a bilingual restatement. The German/English duplication is minor overhead but aids cross-lingual routing; nothing else is wasted.

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?

With four required numeric/boolean params fully documented and read-only annotations, the call mechanics are covered. But with no output schema, the description should state what the check returns (a boolean comparison, a margin, a message), which it never does, leaving a real gap for a validation-style tool.

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 each of the four parameters carries a precise German description, so the schema carries the semantics. The description adds only the high-level notion of a 'selbst gewähltes Messbudget' and does not explain the roles of ab_zusammen_w, ac_zusammen_w, or vergleichbar. Baseline 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 names a concrete action (checking observed simultaneous draw) and a concrete referent (a voluntary household budget), so the verb+resource pair is present. However, it is not clear what the check produces (a verdict? a delta?) and it gives no way to distinguish this from the many sibling household-electricity tools that also compare measured values.

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 only usage signal is an obscure precondition ('Bei drei bestätigten Haushaltsaufgaben'), with no explanation of what that means operationally, no when-not guidance, and no named alternative such as the shared-usage or normalization siblings.

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