Skip to main content
Glama

getecoback-raumklima

brause_angebotszitat_strahlart_einzelwert_maximum

Read-only

Zwei zitierte Durchflusswerte nur mit übereinstimmend belegter Wertart vergleichen — Check mode-specific and product-maximum figures for a common basis.

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": {
      "a_wert_l_min": "<a_wert_l_min>",
      "b_wert_l_min": "<b_wert_l_min>",
      "a_wertart": "<a_wertart>",
      "b_wertart": "<b_wertart>",
      "aktueller_artikelbezug": "<aktueller_artikelbezug>",
      "druckbasis_gleich": "<druckbasis_gleich>",
      "strahl_uebereinstimmend": "<strahl_uebereinstimmend>"
    },
    "name": "brause_angebotszitat_strahlart_einzelwert_maximum"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_wertartYesArt der Angabe A.
b_wertartYesArt der Angabe B.
a_wert_l_minYesVollständig abgelesene Angabe A.
b_wert_l_minYesVollständig abgelesene Angabe B.
druckbasis_gleichYesBeide technischen Werte beziehen sich auf denselben belegten Druck.
aktueller_artikelbezugYesWerte und zugehörige Artikelnummern jeweils verifiziert.
strahl_uebereinstimmendYesBei strahlbezogenen Angaben ist derselbe Strahltyp belegt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this as a read-only, closed-world operation. The description adds the domain rule that comparison is only valid when value types match, but it does not explain the result or failure behavior when preconditions are not met.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with an English gloss and no filler. The bilingual duplication is functional rather than wasteful.

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 7-parameter, all-required validation/comparison tool with no output schema, the description explains the core gating logic but not what the tool returns or what happens when the consistency checks fail. That leaves a meaningful completeness gap.

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% and every parameter has its own description. The description reinforces the role of a_wertart/b_wertart and the supporting evidence flags, but adds no syntax, format, or interpretation beyond what the schema already provides.

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?

States the specific verb 'vergleichen' and object 'zitierte Durchflusswerte', and adds the qualifying condition that the value type must be consistently documented. It names the two figure types ('strahlart', 'produktmaximum'), but does not explicitly contrast itself with any sibling tool.

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

Usage Guidelines4/5

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

Provides a clear precondition: compare only when the value type is consistently evidenced, which implies when not to use it. However, it does not name an alternative tool or describe fallback behavior when that basis is not consistent.

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