Skip to main content
Glama

getecoback-climate-weather

bosch_tat8613_kruemelschublade_oder_broetchenaufsatz_pflege

Read-only

Krümelschublade, Aufsatzbereich und Gehäuse nach sicherem Abkühlen unterscheiden — Match the documented cleaning method to the observed location.

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>",
      "stelle": "<stelle>",
      "abgekuehlt_und_ausgesteckt": "<abgekuehlt_und_ausgesteckt>"
    },
    "name": "bosch_tat8613_kruemelschublade_oder_broetchenaufsatz_pflege"
  }
}

Input Schema

NameRequiredDescriptionDefault
stelleYesWo soll gepflegt werden?
modell_de_bestaetigtYesBosch TAT8613 und deutsche Herstellerunterlagen am betreffenden Gerät oder Angebot bestätigt?
abgekuehlt_und_ausgestecktYesToaster ist vollständig abgekühlt und der Netzstecker gezogen?

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 declare readOnlyHint=true and openWorldHint=false, so the agent knows nothing is mutated and no external lookup happens. The description usefully adds the safety precondition of cooling before handling, but leaves the response form (instructions vs. a decision) and the significance of the model-confirmation gate 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?

Two short clauses with the safety-relevant constraint front-loaded; nothing is padded. The German/English doubling is mildly redundant but each half carries distinct information (scope, then operation).

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 three required parameters, no output schema and a boolean gate on model confirmation, the definition is adequate but thin: it does not state what the agent receives back or how to proceed when modell_de_bestaetigt is false. For a guidance-style tool the missing return-value framing is the main gap.

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 all three parameters and the four-value location enum are already documented in the schema. The description only restates the location categories and the cooling requirement, adding no extra semantics such as which enum value maps to which cleaning method or why the model confirmation is mandatory.

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 the concrete resources (crumb tray, attachment area, housing) and frames the operation as matching a documented cleaning method to the observed location, which an agent can distinguish from the sibling tools about toasting, defrosting or LED reading. The verb is abstract ('match') and never says explicitly that the tool returns cleaning instructions rather than performing the cleaning, keeping it 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 Guidelines3/5

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

Usage is implied through the precondition 'nach sicherem Abkühlen' (after safe cooling) and the location framing, which tells the agent this is a post-use care step. There is no explicit when-to-use vs. alternative, no statement of what to do if the model is unconfirmed, and no pointer to the sibling checks that precede cleaning.

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