Skip to main content
Glama

getecoback-climate-weather

stromvergleich_ausfall_nach_modus

Read-only

Ungleich verteilte Messausfälle in zwei Betriebsmodi sichtbar machen, bevor deren Verbrauch verglichen wird — Assess selective missingness by operating mode rather than global uptime.

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": {
      "a_geplant": "<a_geplant>",
      "a_erfasst": "<a_erfasst>",
      "b_geplant": "<b_geplant>",
      "b_erfasst": "<b_erfasst>",
      "abstand_limit_pp": "<abstand_limit_pp>"
    },
    "name": "stromvergleich_ausfall_nach_modus"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_erfasstYesErfasste Intervalle in A.
a_geplantYesGeplante auswertbare Intervalle im unabhängig dokumentierten Modus A.
b_erfasstYesErfasste Intervalle in B.
b_geplantYesGeplante auswertbare Intervalle in Modus B.
abstand_limit_ppYesEigene Prüfschwelle für den Abstand der Erfassungsquoten in Prozentpunkten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 adds useful framing about the diagnostic intent (per-mode missingness before a consumption comparison) but does not say what the call actually returns — a verdict, a per-mode rate, or a pass/fail against the threshold — which matters since 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?

Two tight clauses with the diagnostic purpose front-loaded and the contrastive framing second. The bilingual restatement is slightly redundant but each half adds a distinct angle (action vs. interpretation), so there is little waste.

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?

All five required parameters are fully documented and the read-only nature is covered by annotations, so the agent can call it correctly. The remaining gap is outcome shape: with no output schema, the description should indicate whether the result is a computed gap value, a boolean verdict, or a per-mode breakdown.

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%, with each of the five parameters (planned vs. captured intervals for modes A and B, plus the percentage-point gap threshold) documented in the schema itself. The description adds no additional meaning about units, expected ratios, or how the threshold is applied, so it neither compensates nor detracts.

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?

States a specific operation on a specific object: making unequally distributed measurement failures in two operating modes visible, and explicitly frames it as selective missingness per mode rather than global uptime. That contrast distinguishes it conceptually from a consumption or uptime comparison, though no sibling tool is named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear sequencing rule — run this before comparing the two modes' consumption — which tells the agent where the tool sits in the workflow. It stops short of stating exclusions or naming an alternative tool to use instead when the failure distribution is already known to be even.

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