Skip to main content
Glama

getecoback-raumklima

bosch_tat8613_memory_nach_stromunterbrechung

Read-only

Beim Wiederanschalten die gespeicherte Röstgradwahl als möglichen Grund für die gelesene Einstellung erkennen — Read what the memory function preserves after power interruption.

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>",
      "vorgang": "<vorgang>",
      "neue_auswahl": "<neue_auswahl>"
    },
    "name": "bosch_tat8613_memory_nach_stromunterbrechung"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorgangYesWas ist seit der letzten dokumentierten Stufe passiert?
neue_auswahlYesSeitdem wurde manuell eine neue Auswahl vorgenommen?
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/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 and the description's 'Read' framing is consistent with it. The description adds domain context — that the memory function may explain a setting seen after re-powering — but says nothing about what the result looks like or how confident/conditional the conclusion is, which matters for a diagnostic tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short clauses, so length is not the problem, but the German and English halves are not parallel: one describes an inference task, the other a read operation. The front-loaded content is the interpretive framing rather than the concrete operation, which slightly obscures the core action.

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?

Three required parameters, full schema coverage, and no output schema mean the definition is minimally sufficient to invoke the tool. It is not sufficient to interpret the response, though: nothing states what 'preserved' means in the answer, how the enum branches change the conclusion, or why model confirmation is required.

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% with self-documenting fields (vorgang enum, neue_auswahl, modell_de_bestaetigt), so the baseline of 3 applies. The description adds no meaning beyond the schema — it never references what happened since the last step, whether a new selection was made, or the model-confirmation gate, all of which drive the answer.

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 English clause 'Read what the memory function preserves after power interruption' gives a recognizable verb and resource, but the German clause frames the tool as 'recognizing a possible reason for the observed setting', which is interpretive rather than operational. An agent can guess the domain (browning-level memory across a power loss) but not precisely what the call produces or how it differs from the many other TAT8613 diagnostic siblings.

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?

The trigger condition is implied by 'Beim Wiederanschalten' (when switching back on after an interruption), which gives a usable context. However, no explicit when-not guidance, prerequisites, or reference to an alternative sibling tool is provided, so routing must be inferred.

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