Skip to main content
Glama

getecoback-raumklima

backofenauszug_paarbeleg_hinweis_auf_andere_ebene

Read-only

Einzeln belegte linke und rechte Schienen eines Angebots mit seiner konkreten Ebenenzuordnung prüfen — Verify that two observed rails actually document the same requested pair and position.

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": {
      "beide_teile_sichtbar": "<beide_teile_sichtbar>",
      "gleiche_paarzuordnung": "<gleiche_paarzuordnung>",
      "geplante_ebene": "<geplante_ebene>",
      "links_ebene": "<links_ebene>",
      "rechts_ebene": "<rechts_ebene>",
      "beide_ebenenbelege": "<beide_ebenenbelege>"
    },
    "name": "backofenauszug_paarbeleg_hinweis_auf_andere_ebene"
  }
}

Input Schema

NameRequiredDescriptionDefault
links_ebeneYesAnhand der Unterlagen belegte linke Position, Platzhalter 1 falls der Ebenenbeleg offen ist.
rechts_ebeneYesAnhand der Unterlagen belegte rechte Position, Platzhalter 1 falls der Ebenenbeleg offen ist.
geplante_ebeneYesFür den eigenen Plan benötigte Ebene.
beide_ebenenbelegeYesSind beide Positionsbelege für dieses Gerät verfügbar?
beide_teile_sichtbarYesSind linke und rechte Seite einzeln am tatsächlich angebotenen Set identifiziert?
gleiche_paarzuordnungYesSind beide Teile vom Hersteller dokumentiert als genau dieses Paar zugeordnet?

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 and the bar is lower. The description adds the semantic that this is a cross-check of two observations against a requested pair, but it says nothing about what the tool reports on a mismatch, even though the tool name ('hinweis_auf_andere_ebene') strongly implies a diagnostic hint output that is never explained.

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 front-loads the purpose, which is good. However, the English sentence largely restates the German one rather than adding information, so a meaningful share of the text does not earn its place.

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?

For a six-required-parameter read-only verification tool with no output schema, the description covers the input side adequately through the schema but leaves the outcome side blank. An agent cannot tell from the description what a successful versus failed pair check produces, which matters given the name's suggestion of a 'hint to another level'.

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 six parameters including the 'bestaetigt/abweichend/offen' enum are already documented in the schema. The description adds no meaning beyond that, such as how the placeholder value 1 for open level evidence interacts with the result — baseline 3 applies when the schema does the heavy lifting.

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 ('prüfen' / 'Verify') and a specific resource ('linke und rechte Schienen eines Angebots' with its 'Ebenenzuordnung'), and states the exact question the tool answers: whether two observed rails document the same requested pair and position. It is clear enough to distinguish from a general single-view tool, but it never names or contrasts the closest sibling ('backofenauszug_einzelansicht_belegt_ebene_oder_satz'), so differentiation is left to inference.

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 by the phrasing 'two observed rails' and 'same requested pair and position' — an agent can infer this is the paired-evidence check rather than a single-part lookup. There is no explicit when-to-use / when-not-to-use statement and no named alternative for the case where only one side is observed.

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