Skip to main content
Glama

getecoback-climate-weather

bosch_tat8613_zwei_leds_roestgrad_ablesen

Read-only

Zwei gleichzeitig angezeigte Röstgradzahlen beim TAT8613 als Zwischenstufe lesen — Decode consecutive odd markings while the selected level is shown.

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>",
      "anzeigephase": "<anzeigephase>",
      "links": "<links>",
      "rechts": "<rechts>"
    },
    "name": "bosch_tat8613_zwei_leds_roestgrad_ablesen"
  }
}

Input Schema

NameRequiredDescriptionDefault
linksYesErste sichtbare Ziffer.
rechtsYesZweite sichtbare Ziffer, bei nur einer 0.
anzeigephaseYesBeobachtete Anzeigephase.
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.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 interpretive rule (odd consecutive markings map to an in-between level) and the display-phase precondition, but says nothing about what the decoded result looks like or what happens with non-consecutive or even markings.

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?

It is short and the core action is front-loaded, but the German sentence and the English sentence are near-verbatim restatements, so roughly half the text is duplication rather than added information.

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 a simple read-only tool, four fully documented required parameters, and no output schema, the definition covers the essentials. However, it never states what the tool returns (the resolved intermediate level value) and omits the model-confirmation prerequisite that the modell_de_bestaetigt parameter enforces.

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 four parameters are already documented in the schema, including the enum for anzeigephase and the 'bei nur einer 0' fallback for rechts. The description adds no further meaning beyond restating the two-digit reading scenario, so the baseline of 3 applies.

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 action: reading two simultaneously displayed browning-level digits on the TAT8613 as an intermediate stage, plus decoding consecutive odd markings. That is concrete enough to distinguish it from siblings about trays, defrosting, or stopping the toasting cycle, though it never names a sibling for contrast.

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 clause 'while the selected level is shown' gives an implicit precondition for use, matching the anzeigephase parameter, but there is no explicit statement of when not to use this tool or which sibling handles the single-digit / progress-display cases.

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