Skip to main content
Glama

getecoback-raumklima

gebrauchtgeraet_testprotokoll_normalfall_nachtrag

Read-only

Bei nachgereichten Vorführläufen erkennen, ob ursprünglich nur positive Beispiele ausgewählt waren — Detect a changed result mix when documented omitted runs are restored.

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": {
      "gleiches_kriterium": "<gleiches_kriterium>",
      "zuerst_gesamt": "<zuerst_gesamt>",
      "zuerst_ok": "<zuerst_ok>",
      "nachtrag_gesamt": "<nachtrag_gesamt>",
      "nachtrag_ok": "<nachtrag_ok>"
    },
    "name": "gebrauchtgeraet_testprotokoll_normalfall_nachtrag"
  }
}

Input Schema

NameRequiredDescriptionDefault
zuerst_okYesDavon für die Aufgabe passend beendet.
nachtrag_okYesDavon für dasselbe Kriterium passend beendet.
zuerst_gesamtYesZuerst gezeigte dokumentierte Läufe.
nachtrag_gesamtYesZusätzliche vorher ausgelassene, nun dokumentierte Läufe.
gleiches_kriteriumYesSind Exemplar, Aufgabe und Kriterium aller zuerst gezeigten und nachgereichten Läufe vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint and openWorldHint annotations already establish that this is a safe, non-open-world computation. The description adds the analytical goal of detecting a changed result mix, but it does not explain the return value or how the comparison result should be interpreted.

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 description is a compact single sentence with the triggering condition front-loaded. The German and English halves are semantically redundant, but the overall text remains short and easy to scan.

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?

The tool has five required inputs and no output schema, so the description carries more burden than usual for explaining what is returned. It clearly describes the analytical scenario but leaves the result format and interpretation implicit.

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?

All five parameters have complete schema descriptions, including the before/after total and OK counts and the 'gleiches_kriterium' boolean. The description does not add further meaning beyond the schema, so the baseline of 3 is appropriate.

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 analytical purpose: detecting a changed result mix when previously omitted documented runs are restored, and checking whether only positive examples were originally selected. It is far more specific than the tool name alone, though it does not explicitly distinguish itself from sibling test-protocol tools.

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 'Bei nachgereichten Vorführläufen' / 'when documented omitted runs are restored' clearly establishes the situation in which this tool applies. It does not name alternatives or exclusions, but the usage context itself is unambiguous.

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