Skip to main content
Glama

getecoback-raumklima

bosch_sbv4ebx00d_nische_tueroeffnung_abgleichen

Read-only

Bosch SBV4EBX00D anhand der deutschen Zeichnung auf gemessene Nische und verbleibende Tiefe bei 90° prüfen — Compare the exact Bosch model’s niche and door-open envelope.

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_belegt": "<modell_belegt>",
      "hoehe_mm": "<hoehe_mm>",
      "breite_mm": "<breite_mm>",
      "tiefe_mm": "<tiefe_mm>",
      "hindernis_mm": "<hindernis_mm>",
      "tiefenbezug_geprueft": "<tiefenbezug_geprueft>"
    },
    "name": "bosch_sbv4ebx00d_nische_tueroeffnung_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoehe_mmYesKleinste nutzbare Höhe der leeren Nische.
tiefe_mmYesKleinste nutzbare Tiefe bis zur festgestellten vorderen Nischenkante.
breite_mmYesKleinste nutzbare Breite der leeren Nische.
hindernis_mmYesFreie horizontale Tiefe vom selben hinteren Bezugspunkt wie die Herstellermaßangabe bis zum Hindernis.
modell_belegtYesIst SBV4EBX00D auf dem Gerät oder in einem eindeutig zugeordneten Produktbeleg bestätigt?
tiefenbezug_geprueftYesWurde der gleiche Bezug wie in der Herstellerangabe für die Tiefe bei 90° geprüft?

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 safety is covered. The description adds that the comparison is against the German manufacturer drawing and is limited to the 90-degree opening position, which is real behavioral context, but it says nothing about what the check produces or how a failed identity confirmation (modell_belegt=false) is handled.

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 sentences, front-loaded with the model number and the operation. The German/English duplication is mildly redundant but keeps the domain terminology precise without bloat.

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?

Six required parameters and no output schema mean the description should at least sketch the nature of the result (a fit verdict, a clearance figure, or a rejection when the model is unconfirmed), and it does not. The measurement-versus-drawing framing is present, but the outcome side of the call is left entirely unstated.

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 coverage is 100%, so the baseline is 3. The description does tie the parameters together conceptually ('gemessene Nische' plus 'verbleibende Tiefe bei 90 Grad'), which frames why height, width, depth, obstacle and depth-reference flags are all required, but it adds no format, tolerance or unit detail 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 names a specific verb (pruefen/compare) and a specific resource (the niche dimensions plus the 90-degree door-open envelope for the exact model SBV4EBX00D). The model specificity distinguishes it from generic sibling checks such as kuehlschrank_tueroeffnung_alltag, though no sibling is named explicitly.

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 scenario is implied: the agent should use this once the niche has been measured and the model identity is established. There is no explicit when-not guidance, no mention of what to do if the model is not confirmed on the appliance, and no routing to alternative check tools for other appliances.

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