Skip to main content
Glama

getecoback-raumklima

bosch_tat8613_roestvorgang_stopp_ende_highlift

Read-only

Stopp, automatisches Anheben und High Lift getrennt einordnen — Distinguish early user cancellation, the observed end and the extraction aid.

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": {
      "modell_de_bestaetigt": "<modell_de_bestaetigt>",
      "beobachtung": "<beobachtung>"
    },
    "name": "bosch_tat8613_roestvorgang_stopp_ende_highlift"
  }
}

Input Schema

NameRequiredDescriptionDefault
beobachtungYesDokumentiertes Ereignis.
modell_de_bestaetigtYesBosch TAT8613 und deutsche Herstellerunterlagen am betreffenden Gerät oder Angebot bestätigt?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered and the description does not need to restate them. What it adds is conceptual: these three phenomena must not be conflated. It does not say what the tool emits (a label? a rationale?) or how an unconfirmed model (modell_de_bestaetigt=false) affects the result, leaving a real gap for a classification tool.

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 with the core distinction front-loaded, followed by an English gloss. The bilingual duplication and the terse dash construction cost a little clarity, but there is no filler.

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

Completeness4/5

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

For a two-parameter, fully documented, read-only classification tool with no output schema and no nesting, the definition covers what is being classified. The missing piece is what the classification produces and how a negative model confirmation is handled, which keeps it just below fully complete.

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 a documented five-value enum, so the baseline is 3. The description does interpret three of those values in domain terms (Stopptaste = early cancellation, automatic lift = observed end, lever lift = extraction aid), which is modest added meaning, but it says nothing about the boolean confirmation gate beyond the schema's own text.

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 operation ('getrennt einordnen' — classify separately) over a specific subject: stop, automatic lifting, and High Lift, and the English gloss enumerates the three cases (early user cancellation, observed end, extraction aid). That maps cleanly onto the enum and separates it from sibling tools like the browning-level or crumb-tray topics. It stops short of saying the tool classifies a supplied observation and returns a category, so it is clear but not fully explicit.

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?

There is no statement of when to call this versus alternatives, no prerequisites, and no mention that the model-confirmation flag must be settled first. The three-way distinction describes content, not call conditions, so an agent must infer usage from the parameter enum alone.

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