Skip to main content
Glama

getecoback-raumklima

bosch_tie20301_latte_macchiato_glas_hoehe_einsetzen

Read-only

Prüft beim Bosch TIE20301 die 130-mm-Glashöhe und ob ein eigenes Latte-Macchiato-Glas gerade eingesetzt werden kann — Check the model’s documented glass height and an observed straight insertion.

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": "<modell>",
      "glas_hoehe_mm": "<glas_hoehe_mm>",
      "stellprobe": "<stellprobe>"
    },
    "name": "bosch_tie20301_latte_macchiato_glas_hoehe_einsetzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständige Bezeichnung des deutschen Geräts.
stellprobeYesGerades Einsetzen, erreichbare stabile Lage und Entnahme wurden am exakten Modell ohne Getränkeausgabe beobachtet.
glas_hoehe_mmYesAm höchsten Punkt gemessene Glashöhe beim benötigten geraden Stand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 this is a safe, closed-world check. The description is consistent with that and adds the framing that it verifies a documented height against an observation, but it discloses nothing further about verdict semantics or confidence handling.

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?

A single compact sentence with the target model and measurement front-loaded. The bilingual German/English duplication adds slight redundancy but also resolves an ambiguous phrase, so it largely earns its place.

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 three-parameter, fully documented, read-only check with no output schema, the definition covers what the tool inspects and what the inputs mean. Only the shape of the verdict is left unstated, which is a minor 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 the three parameters and both enums are already fully documented in-schema. The description only contributes the concrete 130-mm target value and the notion of a user's own glass, which is marginal beyond the schema.

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 uses a specific verb ("Prüft") plus two concrete resources: the documented 130-mm glass height and whether a straight insertion of a user's own latte-macchiato glass is possible. That is far more specific than the tool name's keyword string, though it does not distinguish itself from any named sibling.

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 only implied: check glass height and insertion feasibility for the TIE20301. There is no explicit statement of when to prefer this over the many sibling Bosch checks, and no exclusions or prerequisites.

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