Skip to main content
Glama

getecoback-climate-weather

pc_laufpaar_startzustand_vorherige_arbeit

Read-only

Für einen Vergleich zweier identischer PC-Aufgaben unterscheiden, ob jeweils direkt davor Leerlauf oder eine andere Aufgabe dokumentiert war — Check thermal carryover from the last recorded workload rather than the current output 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": {
      "a_vorzustand": "<a_vorzustand>",
      "b_vorzustand": "<b_vorzustand>",
      "vorherige_aufgabe_gleich": "<vorherige_aufgabe_gleich>",
      "gleiche_pruefaufgabe": "<gleiche_pruefaufgabe>"
    },
    "name": "pc_laufpaar_startzustand_vorherige_arbeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_vorzustandYesZustand unmittelbar vor Lauf A aus der vollständigen vorangegangenen Aufzeichnung.
b_vorzustandYesZustand unmittelbar vor Lauf B aus der vollständigen vorangegangenen Aufzeichnung.
gleiche_pruefaufgabeYesDie beiden eigentlichen vollständigen Vergleichsläufe sind deckungsgleich geplant und dokumentiert.
vorherige_aufgabe_gleichYesWenn zuvor beide aktiv waren, ist auch die vorherige Aufgabe vergleichbar.

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 declare readOnlyHint=true and openWorldHint=false, so safety and scope are settled by structured data. The description contributes the non-obvious diagnostic rationale (thermal carryover, prior workload rather than current output), which is real added context. It says nothing about what the tool returns or how an 'offen' input is treated, so it stops at a 3.

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 compact clauses, with the comparison condition front-loaded and the rationale second. The English half largely restates the German half, which is mild redundancy, but it does add the 'carryover vs. current output' framing rather than repeating verbatim. No filler beyond that.

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-parameter, fully required, fully documented read-only judgement tool, the description covers what to check and why. The notable gap is that there is no output schema, so the description should indicate what result the tool yields (a verdict, a pair classification, or nothing) and how 'offen' is resolved — neither is addressed.

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 every parameter carries its own German description plus enums for the two state fields, so the schema does the heavy lifting. The description adds the framing that both states are taken 'aus der vollständigen vorangegangenen Aufzeichnung' and must be compared symmetrically, but gives no per-parameter guidance beyond that. Baseline 3 applies.

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: for a comparison of two identical PC tasks, determine whether idle time or another task was recorded immediately before each run, and it frames the reason (thermal carryover). That is a specific verb-plus-resource statement an agent can act on. It does not differentiate itself from the many similarly named pc_* siblings, which is the only thing keeping it below 5.

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 implied rather than stated: the tool is for the situation where two runs of the same task are being compared and prior-state contamination is suspected, and the English clause adds the heuristic 'check carryover from the last workload rather than the current output alone.' There is no explicit when-not condition and no named alternative among the numerous sibling tools, so the agent must infer the boundary itself.

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