Skip to main content
Glama

getecoback-raumklima

gebrauchtgeraet_vorfuehrung_kaltstart_nur_belegt

Read-only

Bezeichneten Start nach Ruhe von einer Fortsetzung aus dem bereits betriebenen Zustand trennen — Distinguish a demonstrated cold start from an already-running unit.

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": {
      "voraussetzung_belegt": "<voraussetzung_belegt>",
      "geforderter_ruhezustand": "<geforderter_ruhezustand>",
      "neu_start_gesehen": "<neu_start_gesehen>",
      "vorheriger_lauf_beobachtet": "<vorheriger_lauf_beobachtet>"
    },
    "name": "gebrauchtgeraet_vorfuehrung_kaltstart_nur_belegt"
  }
}

Input Schema

NameRequiredDescriptionDefault
neu_start_gesehenYesIst der anschließende tatsächliche Start im selben Ablauf sichtbar?
voraussetzung_belegtYesIst die Startvoraussetzung laut Anleitung oder vereinbartem Vergleich für das konkrete Vorführziel dokumentiert?
geforderter_ruhezustandYesIst der vorherige Ruhe- oder Ausgangszustand dokumentiert?
vorheriger_lauf_beobachtetYesWar unmittelbar vorher ein Lauf zu sehen, der dem geforderten Ausgangszustand widerspricht?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

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

The annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description owes the agent the semantic behavior. It never states how the four booleans combine into an outcome, nor what a negative or conflicting result means, and with no output schema the return shape is entirely undisclosed.

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?

A single front-loaded sentence with the core distinction stated first. The German and English phrasings largely duplicate each other, which costs a little space but does aid disambiguation of the very compressed terminology.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a four-required-parameter evaluation tool with no output schema, so the description is the only place where outcome semantics could be explained — and it is silent on them. An agent knows what question the tool asks but not what it hands back or how to interpret edge cases.

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 boolean's meaning is already documented in the schema; the description adds nothing about parameter interaction. Baseline 3 applies because the schema carries the load.

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 specific discrimination task — separating a genuine cold start (start after rest) from a continuation of an already-running unit — which is more than a restatement of the name. It stops short of saying what the tool mechanically produces (a verdict? a classification?) or how it differs from the numerous sibling evidence-checking tools.

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 decision the tool performs; there is no explicit 'use when' clause, no prerequisite (e.g., that evidence must already be documented), and no mention of alternative or adjacent tools. An agent can infer the situation but must guess at the trigger conditions.

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