Skip to main content
Glama

getecoback-climate-weather

pc_leistungsabfall_und_begrenzungsmeldung

Read-only

Bei einem langsamer gewordenen identischen Lauf eine ausdrückliche Temperaturmeldung von anderen Ursachen und fehlenden Daten trennen — Distinguish a recorded thermal-limit signal from slow work alone.

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": {
      "arbeit_gleich": "<arbeit_gleich>",
      "bezug_ausgaben_pro_min": "<bezug_ausgaben_pro_min>",
      "probe_ausgaben_pro_min": "<probe_ausgaben_pro_min>",
      "protokollgrund": "<protokollgrund>"
    },
    "name": "pc_leistungsabfall_und_begrenzungsmeldung"
  }
}

Input Schema

NameRequiredDescriptionDefault
arbeit_gleichYesAufgabe, Auflösung und Ausgabe sind gegenüber der Bezugsprobe vergleichbar.
protokollgrundYesNur den im Geräteprotokoll für denselben Abschnitt ausdrücklich gelieferten Grund wählen.
bezug_ausgaben_pro_minYesGemessener Arbeitsdurchsatz der Bezugsprobe.
probe_ausgaben_pro_minYesEntsprechend gemessener Durchsatz in der untersuchten Probe.

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?

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the substantive behavioral stance that the thermal signal must be 'ausdrücklich' (explicitly recorded) and must be separated from missing data, which tells the agent the tool will not infer throttling from slowness alone. It still does not say what result is returned when the protocol reason is 'keine Angabe'.

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?

A single sentence of appropriate length, but the bilingual German/English duplication is wasteful: the English clause is a loose paraphrase that drops the 'andere Ursachen und fehlende Daten' nuance, so the second half does not fully earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Four required parameters, a four-value enum, and no output schema mean the description must at least signal what the tool returns and how 'keine Angabe' is treated. It does neither, leaving the agent unable to predict the result of a call it is otherwise expected to make confidently.

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 four parameters (comparability flag, baseline throughput, probe throughput, protocol reason enum) are documented in the schema itself. The description contributes nothing about parameter meaning, which is acceptable at full coverage but adds no value beyond the baseline.

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 states a discrimination task (separating an explicit thermal-limit message from other causes and missing data) but never says what the tool actually produces or does with the four inputs. The verb is interpretive rather than operational, so an agent knows the topic but not the outcome.

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 trigger condition is stated: an identical run that has become slower ('Bei einem langsamer gewordenen identischen Lauf'). It also implies the tool should not be used to explain slowness by causes other than a recorded thermal limit. However, no alternative sibling tool is named and no exclusion or prerequisite is given beyond that single scenario.

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