Skip to main content
Glama

getecoback-raumklima

glassvac_set_saugkoepfe_nachweis_offene_position

Read-only

Prüfe anhand zweier gelieferter Köpfe, ob der nachgewiesene GlassVAC-Lieferumfang vollständig ist — Audit the two nozzle roles in a confirmed GlassVAC set

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": {
      "paketkennung": "<paketkennung>",
      "grosser_kopf": "<grosser_kopf>",
      "kleiner_kopf": "<kleiner_kopf>"
    },
    "name": "glassvac_set_saugkoepfe_nachweis_offene_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
grosser_kopfYesGroßer Saugkopf liegt laut Sichtkontrolle vor
kleiner_kopfYesKleiner Saugkopf liegt laut Sichtkontrolle vor
paketkennungYesBosch-Paketkennung des konkreten Geräts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already state readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the check is a completeness audit over two nozzle roles, but says nothing about what a result conveys (e.g. which positions count as open) or how 'offen' is treated — the main behavioral question for this 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?

The verb and condition are front-loaded and the sentence is short, but the English half largely restates the German half rather than extending it, so roughly half the text is redundant. No wasted clauses beyond that duplication.

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 enum parameters with no output schema means the description should ideally convey what verdict or structure comes back, especially given the 'offene_position' framing. The audit intent is conveyed adequately, but the result side is left entirely to inference.

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% with all three parameters enum-documented, so the baseline is 3. The description maps 'zweier gelieferter Köpfe' onto the two head parameters but never mentions 'paketkennung' or explains what belegt/ausgeschlossen/offen mean for the completeness verdict, so it adds only marginal meaning 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 German sentence gives a specific verb ('Prüfe') and object ('nachgewiesener GlassVAC-Lieferumfang', checked via two delivered heads), so an agent knows this is a completeness audit of a nozzle set. It does not differentiate itself from any named alternative, and the tool name's 'offene_position' angle is not reflected in the description text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

Usage is only implied by the phrase 'anhand zweier gelieferter Köpfe' and 'in a confirmed GlassVAC set'; there is no explicit when-to-use condition, no when-not-to-use, and no sibling tool is named as the alternative. The agent must infer the trigger situation entirely.

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