Skip to main content
Glama

getecoback-raumklima

gebrauchtgeraet_test_reihenfolge_nutzermodus_wiederfinden

Read-only

Eine gezeigte Funktion auf unabhängige Wiederholbarkeit der bestätigten Bedienfolge prüfen — Check whether observed success depended on an unrecorded operator action.

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": {
      "regulaere_folge_bestaetigt": "<regulaere_folge_bestaetigt>",
      "ergebnisse_gleich": "<ergebnisse_gleich>",
      "eingriff_a": "<eingriff_a>",
      "eingriff_b": "<eingriff_b>"
    },
    "name": "gebrauchtgeraet_test_reihenfolge_nutzermodus_wiederfinden"
  }
}

Input Schema

NameRequiredDescriptionDefault
eingriff_aYesBeobachteter zusätzlicher Eingriff in Wiederholung A.
eingriff_bYesBeobachteter zusätzlicher Eingriff in Wiederholung B.
ergebnisse_gleichYesWar das relevante Ergebnis in zwei beobachteten Wiederholungen gleich?
regulaere_folge_bestaetigtYesSind Voraussetzungen und zulässige Bedienfolge für den vorgesehenen Modus bekannt?

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 the safety profile is covered. The description adds the analytical purpose (isolating unrecorded operator intervention), but says nothing about what the evaluation produces or how the four inputs combine into a verdict, so it adds moderate context only.

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 core judgment criterion front-loaded. The German/English duplication is slightly redundant, though the English does add the key nuance about unrecorded operator action rather than simply translating.

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?

With four required parameters and no output schema, the description should say more about what the tool returns and how the fields interact (e.g. what happens when the sequence is not confirmed). It is adequate to identify the tool's purpose but thin for a judgment-producing, boolean-heavy tool.

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%, including enum values for eingriff_a/eingriff_b, so the schema carries parameter meaning. The description does not reference any parameter or explain how 'kein' versus 'nicht_zugeordnet' affects the reproducibility judgment; the 3 baseline 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 gives a specific verb (prüfen/check) and object (reproducibility of a confirmed operating sequence), and the English gloss sharpens the intent: determine whether an observed success depended on an unrecorded operator action. What is missing is any differentiation from the many sibling 'reihenfolge' tools, so an agent cannot tell from the text alone which sequence-related tool applies.

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: you run this after a function has been demonstrated and you suspect the success was not independently repeatable. There is no explicit when-to-use, no prerequisites, and no named alternative among the numerous sibling sequence tools.

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