Skip to main content
Glama

getecoback-climate-weather

pc_temperaturmaximum_aufgaben_nachlauf

Read-only

Das erste protokollierte Temperaturmaximum als Last, Nachlauf oder nicht zuordenbare Messung einordnen — Locate a logged PC temperature maximum relative to load and measured cooldown.

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": {
      "aufgabe_ab_s": "<aufgabe_ab_s>",
      "aufgabe_bis_s": "<aufgabe_bis_s>",
      "nachlauf_bis_s": "<nachlauf_bis_s>",
      "maximum_s": "<maximum_s>",
      "uhren_und_log_geprueft": "<uhren_und_log_geprueft>"
    },
    "name": "pc_temperaturmaximum_aufgaben_nachlauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
maximum_sYesErstes protokolliertes Auftreten des höchsten erfassten Werts derselben Sensorquelle.
aufgabe_ab_sYesBeginn der beobachteten Aufgabe auf der gemeinsamen Zeitachse.
aufgabe_bis_sYesEnde dieser Aufgabe.
nachlauf_bis_sYesEnde des lückenlos anschließenden beobachteten Nachlaufs.
uhren_und_log_geprueftYesZeitbezug und Abdeckung sind geprüft, Maximum ist eine beobachtete Ablesung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safety is covered. The description adds genuine behavioral information beyond them by disclosing that the result is a three-way classification (load / cooldown / unassignable), which no structured field states. However, it says nothing about preconditions such as verified clock reference and log coverage, or about what happens when windows overlap or the maximum falls outside both.

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?

The content is short and front-loaded, but it is the same sentence rendered twice (German and English) without either version adding information the other lacks. There is no wasted padding, yet the duplication means it is efficient in length only, not in information density.

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

Completeness4/5

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

With five fully documented required parameters, no output schema, and read-only annotations, the definition covers what is needed to invoke the tool. The three named outcome classes effectively substitute for a missing output schema, though the description could have stated how a peak inside both windows is resolved.

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 five parameters (including the clock/log verification boolean) are already explained in German. The description only restates the load and cooldown framing at a high level and adds no format, boundary, or ordering semantics 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 (classify the first logged temperature maximum) and its frame of reference (load window vs. measured cooldown), plus the fallback class 'nicht zuordenbare Messung'. That is enough to distinguish it from sibling pc_* tools that deal with windows, sensor mixing, or peak ordering, though the dual 'einordnen/Locate' wording creates mild ambiguity about whether it classifies or merely finds a timestamp.

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?

There is no when-to-use or when-not guidance and no reference to any alternative tool, even though many pc_* siblings cover adjacent timing questions (e.g. pc_cpu_gpu_gleiches_zeitfenster_spitzenreihenfolge, pc_sensorquellen_cpu_gpu_wechsel_nicht_verketten). The agent must infer from the name alone whether this is the right tool for a given peak.

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