Skip to main content
Glama

getecoback-raumklima

pulsify_artikel_strahlart_techniktabelle_drei_bar

Read-only

Dokumentierten hansgrohe-Pulsify-Wert für genaue Artikelnummer, Strahlart und 3-bar-Bezug ausgeben — Read the exact DE technical row rather than a series headline.

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": {
      "artikel": "<artikel>",
      "identitaet_belegt": "<identitaet_belegt>",
      "strahlart": "<strahlart>",
      "druckbezug_bar": "<druckbezug_bar>"
    },
    "name": "pulsify_artikel_strahlart_techniktabelle_drei_bar"
  }
}

Input Schema

NameRequiredDescriptionDefault
artikelYesAm Artikel verifizierte deutsche Artikelnummer.
strahlartYesAbgelesene gewünschte Strahlart.
druckbezug_barYesAus der zu vergleichenden Quelle belegter Druck in bar. Bei fehlendem Wert 0 eingeben.
identitaet_belegtYesIst diese Nummer an Gerät, Verpackung oder eindeutigem Angebotsbeleg bestätigt?

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. The description adds that only *documented* values are returned, which usefully signals it is an evidence lookup rather than an inference, but it never says what happens with 'andere_oder_unbekannt' or 'unbekannt' inputs or what the response looks like.

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 the disambiguating clause is front-loaded, but the German clause largely restates the parameter list and then the English gloss repeats the same idea. Two of the phrases duplicate what the schema and the name already convey.

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 simple read-only lookup with full schema coverage and no output schema, this is close to sufficient. The remaining gaps are edge behavior for unknown article/spray values and what a returned 'documented value' consists of, which an agent cannot infer.

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 enum values and ranges; baseline is 3. The description restates three of them (Artikelnummer, Strahlart, 3-bar-Bezug) without adding syntax or meaning, and says nothing about the verification gate implied by identitaet_belegt.

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 (ausgeben / read) and a specific resource (a documented hansgrohe Pulsify technical row), and explicitly scopes it as the exact article row rather than a series headline. It is differentiated from a headline/series lookup, though the dense compound jargon keeps it from being instantly legible.

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 phrase 'rather than a series headline' implies the condition under which this tool is correct (exact, verified article data), but no alternative tool is named and no when-not case is stated. Guidance must be inferred from the contrast clause rather than read directly.

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