Skip to main content
Glama

getecoback-raumklima

stromprotokoll_netzausfall_nulllast_einordnen

Read-only

Fehlende Stromlogger-Abschnitte mit unabhängig belegtem Netzausfall von ungeklärten Ausfällen trennen — Classify missing import records without treating all missing time as zero.

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": {
      "fehlend_min": "<fehlend_min>",
      "ohne_netzzufuhr_min": "<ohne_netzzufuhr_min>",
      "import_only": "<import_only>"
    },
    "name": "stromprotokoll_netzausfall_nulllast_einordnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
fehlend_minYesDokumentierte Dauer aller fehlenden Loggerabschnitte.
import_onlyYesMessgröße ist ausschließlich aus dieser Versorgung importierter Strom?
ohne_netzzufuhr_minYesDavon unabhängig als ohne Stromzufuhr belegt, passend zur gemessenen Netzimportgrenze.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/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 adds a substantive behavioral rule beyond them: missing time must not be treated as zero consumption, and only independently documented outage periods may be separated out. It does not say what the returned classification looks like, but the policy constraint is the important part.

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, front-loaded with the classification action and closed by the key caveat, with an English gloss for clarity. No wasted wording, though the German-first phrasing plus gloss doubles the length slightly.

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 classification tool with no output schema, the description never indicates what the result is — a category assignment, a split of minutes, or a boolean. The domain rule against zeroing missing time is complete, but the return behavior is left entirely to inference.

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 the schema already documents all three parameters. The description does add interpretive value by tying the evidence threshold to the measured grid import boundary, reinforcing that 'ohne_netzzufuhr_min' must be corroborated rather than assumed — but it adds no units, ranges, or consistency rules beyond that.

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 concrete operation — separating missing logger intervals that have independently evidenced grid outage from unexplained outages — rather than restating the cryptic German tool name. It is clear what the tool does, though it does not explicitly position itself against the sibling 'stromprotokoll_lueckensumme_anker', which covers adjacent gap-summing territory.

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?

Usage context is implied by the domain framing (missing import records, outage evidence), but there is no explicit when-to-use versus when-not, and no named alternative for the case where a plain gap sum is wanted. An agent must infer the routing decision from the scenario wording.

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