Skip to main content
Glama

getecoback-raumklima

bosch_sks62e32eu_glastruebung_ablesbarer_beleg

Read-only

Beim kompakten Bosch anhaltende Glastrübung von abwischbarer Auflage unterscheiden — Decide which evidence branch applies without diagnosing irreversible damage.

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": {
      "anleitung_bestaetigt": "<anleitung_bestaetigt>",
      "zustand": "<zustand>",
      "glasdeklaration": "<glasdeklaration>"
    },
    "name": "bosch_sks62e32eu_glastruebung_ablesbarer_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
zustandYesBereits festgestellter Zustand derselben Gläser.
glasdeklarationYesGelesene Angabe am exakten Glas oder in seinen Unterlagen.
anleitung_bestaetigtYesGenaue deutsche Modellkennung und genannte Anleitung am konkreten Gerät abgeglichen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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, so the safety profile is covered. The description adds the scope boundary that this is a branch-selection step rather than a damage diagnosis, which is useful, but says nothing about how the decision is made or what the result conveys; with no output schema, that leaves a gap.

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 short clauses joined by a dash, with the operative instruction front-loaded after a brief German framing phrase. No filler sentences, though the opening clause is syntactically awkward and could be tightened.

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 three-parameter, fully-described classification tool with readOnly annotations and no output schema, the description supplies the decision framing and one scope limit. It does not explain what 'evidence branch' means in outcome terms or how the confirmation flag interacts with the branch choice, leaving moderate gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and two parameters are enums with self-documenting values ('abwischbare_auflage' vs 'anhaltende_truebung'), so the schema carries most of the meaning. The description's mention of distinguishing persistent cloudiness from wipeable deposit does loosely map to those enum branches, adding slight reinforcement, though it says nothing about 'anleitung_bestaetigt'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific operation (distinguishing persistent glass cloudiness from a wipeable deposit and deciding which evidence branch applies), which is more than a restatement of the name. However, the phrasing is dense German with an odd leading clause ('Beim kompakten Bosch...') and gives no differentiation from the many sibling '*_beleg' decision 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 implied: call this when a glass condition has been observed and one of the enum branches must be selected. The description adds one genuine exclusion — it should not be used to diagnose irreversible damage — but offers no explicit when-not rules or named alternatives among the sibling 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