Skip to main content
Glama

getecoback-raumklima

pc_benchmark_aufzeichnung_mindestlauf_ausschluss

Read-only

Prüfen, ob abgebrochene Aufnahmen überproportional in einer Lastgruppe liegen — Compare incomplete PC runs by workload group before using performance averages.

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_begonnen": "<a_begonnen>",
      "a_unvollstaendig": "<a_unvollstaendig>",
      "b_begonnen": "<b_begonnen>",
      "b_unvollstaendig": "<b_unvollstaendig>"
    },
    "name": "pc_benchmark_aufzeichnung_mindestlauf_ausschluss"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_begonnenYesBegonnene Proben der ersten gleich definierten PC-Aufgabe.
b_begonnenYesBegonnene Proben der zweiten gleich definierten Aufgabenklasse.
a_unvollstaendigYesDavon ohne verlangten Ergebnis- und Temperaturendpunkt.
b_unvollstaendigYesDavon entsprechend unvollständige Proben.

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, which matches the described pure comparison, so no contradiction exists. The description adds the analytical intent (detect disproportionate incomplete-run shares) but never says what the verdict looks like — boolean, ratio, per-group breakdown — and there is no output schema to cover that 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 German clause front-loads the check, but the English sentence largely duplicates it while adding the usage cue, producing bilingual redundancy. It is short, yet not every clause earns a distinct place.

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-count read-only computation with fully documented parameters the definition is adequate, but with no output schema it leaves the interpretation of 'überproportional' (any threshold? ratio vs. verdict?) unexplained. An agent knows what to pass in but not exactly what it will get back or how to read a positive result.

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 each of the four counts (begun vs. incomplete, group A vs. B) is already documented in the schema. The description contributes only the notion of grouping by 'Lastgruppe', not any clarification of units, pairing, or acceptable value ranges beyond what the schema states; 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 states a concrete check: whether aborted/incomplete PC runs are over-proportionally concentrated in one workload group, with the two comparison groups named. It is clearly distinct from the sibling benchmark tools, though the German and English halves restate the same idea rather than adding specificity.

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?

The phrase 'before using performance averages' gives an explicit trigger condition for when to call it — a pre-check on data quality ahead of averaging. It does not name an alternative tool or state when the check is unnecessary, so it stops short of full when/when-not 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