Skip to main content
Glama

getecoback-raumklima

pc_displayphase_puffer_zweiseitig

Read-only

Bei einem Wärmeprotokoll die getrennt gewählten Abstände vor und nach einem bekannten Bildschirmwechsel aus der Vergleichsphase heraushalten — Trim an observed desk thermal log around a known display transition.

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": {
      "protokoll_ab_s": "<protokoll_ab_s>",
      "displaywechsel_s": "<displaywechsel_s>",
      "protokoll_bis_s": "<protokoll_bis_s>",
      "abstand_vorher_s": "<abstand_vorher_s>",
      "abstand_nachher_s": "<abstand_nachher_s>"
    },
    "name": "pc_displayphase_puffer_zweiseitig"
  }
}

Input Schema

NameRequiredDescriptionDefault
protokoll_ab_sYesBeginn eines sonst gleichartig protokollierten PC-Abschnitts.
protokoll_bis_sYesEnde des Abschnitts.
abstand_vorher_sYesEigenes vorab gewähltes Ausschlussfenster vor der beobachteten Umschaltung.
displaywechsel_sYesZeitpunkt des bekannten Bildschirmzustandswechsels.
abstand_nachher_sYesEigenes vorab gewähltes Ausschlussfenster nach dem Wechsel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 safety is covered elsewhere. The description adds the meaningful semantic that the margins are chosen separately for before and after and that the affected span is kept out of the comparison phase, but it says nothing about what the result looks like, what happens when the margins exceed the logged range, or whether the transition must lie inside [protokoll_ab_s, protokoll_bis_s].

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?

The operative intent is front-loaded in a single German sentence, followed by a compact English gloss. The bilingual pairing is mildly redundant but short, and nothing else is wasted.

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 five-required-parameter transform with full schema coverage and no output schema, the description conveys enough to attempt a call. What it leaves thin is the outcome: whether the tool returns a trimmed interval, filtered samples, or a count, and how boundary cases are handled.

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 the five numeric parameters are already documented individually with ranges. The description adds only the grouping insight that abstand_vorher_s and abstand_nachher_s are an independently selected exclusion pair rather than derived values; it gives no units, ordering constraints, or overlap rules 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 concrete operation on a concrete object: excluding separately chosen buffer intervals before and after a known display switch from a thermal comparison log. That is a specific verb+resource, not a restatement of the name, though it never contrasts itself with near-neighbours such as pc_leistungsprotokoll_ansaugfenster_wechselabstand.

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 is only implied by the phrase 'Bei einem Wärmeprotokoll ... heraushalten' — the agent can infer that this applies when a thermal log contains a known display transition plus user-chosen margins. There is no explicit statement of when not to use it, no mention of alternatives, and no prerequisite guidance.

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