Skip to main content
Glama

getecoback-raumklima

spueler_bedienfeld_sichtprobe_front_und_offen

Read-only

Eine Bedienanzeige bei geschlossener und teilweise geöffneter Front getrennt nach eigener Sichtprobe ausweisen — Check when a status display is actually visible to the user.

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": {
      "anzeigevariante_belegt": "<anzeigevariante_belegt>",
      "geschlossen_sichtbar": "<geschlossen_sichtbar>",
      "offen_sichtbar": "<offen_sichtbar>",
      "nutzungsstand_gleich": "<nutzungsstand_gleich>"
    },
    "name": "spueler_bedienfeld_sichtprobe_front_und_offen"
  }
}

Input Schema

NameRequiredDescriptionDefault
offen_sichtbarYesDie Information war von derselben Position im bestätigten geöffneten Zustand sichtbar.
geschlossen_sichtbarYesDie gewünschte Statusinformation war beim beobachteten Gerät von der vorgesehenen Position geschlossen sichtbar.
nutzungsstand_gleichYesWar jeweils derselbe Anzeigenzustand, Licht und Standort vergleichbar?
anzeigevariante_belegtYesDie am Modell dokumentierte Anzeigevariante wurde geprüft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds that the assessment is based on one's own visual check and separates closed-front from partially-open-front visibility, but it does not explain what result or decision the tool produces from the four booleans. With annotations carrying the basic behavior, this is adequate but not rich.

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 definition is short and front-loads the scenario being assessed. The bilingual restatement is slightly redundant, but it is not verbose and every clause relates to the visibility check.

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 read-only four-boolean visual-assessment tool with fully documented parameters, the description covers the scenario and the closed/open comparison. However, it does not clarify the expected outcome of the operation, and the agent is left to infer how the four required booleans are interpreted together.

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 parameter is already documented in the input schema. The description reinforces the closed/partially-open distinction and the idea of separate visual checks, but it adds no new syntax, decision rules, or combined semantics beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 resource and condition: a control display (Bedienanzeige) assessed with the front closed and partially open, using a separate visual check. This is clearer than a tautology and lets an agent distinguish it from unrelated sibling checks. It does not explicitly differentiate itself from nearby spueler visual-probe siblings, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is used to check whether a status display is actually visible to the user, but it gives no explicit when-to-use or when-not-to-use guidance. It does not name an alternative sibling tool or explain what conditions should lead an agent to choose this tool over another Sichtprobe operation.

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