Skip to main content
Glama

getecoback-climate-weather

pc_leistungsprotokoll_ansaugfenster_wechselabstand

Read-only

Eine Temperaturablesung nur einer bekannten PC-Aufgabe zuordnen, wenn pünktliche Lastgrenze und bekannter Messverzug das erlauben — Keep delayed thermal samples out of mixed workload phases.

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_start_s": "<aufgabe_start_s>",
      "aufgabe_ende_s": "<aufgabe_ende_s>",
      "thermik_ablesung_s": "<thermik_ablesung_s>",
      "maximaler_verzug_s": "<maximaler_verzug_s>"
    },
    "name": "pc_leistungsprotokoll_ansaugfenster_wechselabstand"
  }
}

Input Schema

NameRequiredDescriptionDefault
aufgabe_ende_sYesEnde des Aufgabenabschnitts auf derselben Achse.
aufgabe_start_sYesBeginn des nachweislich zusammenhängend gleichartigen Aufgabenabschnitts.
maximaler_verzug_sYesDokumentierte maximale Verzögerung der protokollierten Ablesung.
thermik_ablesung_sYesZeitstempel der betreffenden Temperaturablesung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 the decision condition and the mixed-phase exclusion, which is useful behavioral context. However, it never says what happens when the condition fails (rejection, null result, error) and no output schema exists to answer that, leaving a meaningful behavioral gap.

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 core condition is front-loaded in the German clause, but the English fragment 'Keep delayed thermal samples out of mixed workload phases' largely restates the exclusion rather than adding new information. The bilingual duplication costs space without proportional value.

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 four-required-parameter decision tool with no output schema, the description explains the gating condition and the exclusion but omits return semantics and failure behavior, which an agent needs to interpret results correctly. Annotations cover read-only safety, so the remaining gap is the result contract rather than permissions.

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 all four parameters carry their own units, bounds, and German explanations. The description introduces the concepts of task boundary and measurement delay but adds no format, ordering, or edge-case detail beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific operation: assigning a single temperature reading to exactly one known PC task, gated by a condition (punctual load boundary plus known measurement delay). It distinguishes the intent from broader thermal-correlation siblings by insisting on a single assignment and excluding mixed phases. It stops short of saying what the tool returns (a verdict, an assignment, or a rejection), which keeps it from a 5.

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?

It gives an explicit precondition — 'wenn pünktliche Lastgrenze und bekannter Messverzug das erlauben' — and an exclusion: delayed samples must stay out of mixed workload phases. This is real when-to-use guidance rather than implied usage. It does not name an alternative sibling for the mixed-phase case, which is the only missing element.

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