Skip to main content
Glama

getecoback-raumklima

fenstersauger_wv3_enge_felder_duesenreserve

Read-only

Prüfe beim WV 3 Comfort Precision+, welche bestätigte Düse in zwei freie Glasbreiten passt — Match confirmed WV 3 nozzle widths to two measured glass openings

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": {
      "paket_16336980": "<paket_16336980>",
      "schmale_duese_vorhanden": "<schmale_duese_vorhanden>",
      "glas_a_mm": "<glas_a_mm>",
      "glas_b_mm": "<glas_b_mm>"
    },
    "name": "fenstersauger_wv3_enge_felder_duesenreserve"
  }
}

Input Schema

NameRequiredDescriptionDefault
glas_a_mmYesEngste freie Breite von Glasfeld A, nach Abzug der Messreserve
glas_b_mmYesEngste freie Breite von Glasfeld B, nach Abzug der Messreserve
paket_16336980YesExakte Paketkennung 1.633-698.0 ist belegt
schmale_duese_vorhandenYesDie dokumentierte 170-mm-Düse ist im konkreten Angebot bestätigt

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 the safety profile is covered. The description adds little beyond that: it hints that only a 'bestätigte' (confirmed) nozzle counts, but does not say what the result looks like when no nozzle fits, nor any constraint on the measurement reserve already subtracted from the inputs.

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?

It is a single front-loaded sentence with no filler. The German/English duplication of the same content is mild redundancy rather than waste, since it does not obscure the task.

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 four fully documented parameters and trivial read-only annotations, the input side is complete. However, there is no output schema, and the description never states what a successful match returns (e.g. which nozzle maps to field A vs field B, or the no-match case), leaving a gap for a matching tool.

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 with ranges and meaning. The description only restates that two free glass widths are involved and that the nozzle must be confirmed, adding no syntax or interpretation beyond the schema; baseline 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 check (which confirmed nozzle fits), a specific device model (WV 3 Comfort Precision+), and the two measured glass widths, so the agent can tell this apart from the WV 8 sibling. It stops short of naming that WV 8 sibling as the alternative, so sibling differentiation is only partial.

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 implied by the phrasing 'Prüfe ... welche bestätigte Düse ... passt', i.e. call this when you need to verify nozzle fit. There is no explicit when-not condition, no prerequisite statement (e.g. that the package ID must be confirmed first), and no pointer to an alternative tool.

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