Skip to main content
Glama

getecoback-climate-weather

brause_werbeaussage_serienwert_technikwert_zuordnen

Read-only

Einen Serienhöchstwert und eine technische Artikelzeile nach ihrem Geltungsbereich auseinanderhalten — Resolve showroom headline versus an exact technical row.

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": {
      "werbewert_l_min": "<werbewert_l_min>",
      "technikwert_l_min": "<technikwert_l_min>",
      "technik_artikel_geprueft": "<technik_artikel_geprueft>",
      "werbung_gleicher_artikel": "<werbung_gleicher_artikel>",
      "gleiche_bedingung_und_wertart": "<gleiche_bedingung_und_wertart>"
    },
    "name": "brause_werbeaussage_serienwert_technikwert_zuordnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
werbewert_l_minYesAbgelesener Serien-Werbewert in Litern pro Minute.
technikwert_l_minYesAbgelesener Wert aus der technischen Zeile in Litern pro Minute.
technik_artikel_geprueftYesDie technische Zeile passt zur vollständigen Artikelnummer.
werbung_gleicher_artikelYesDer Werbewert ist nachweislich für diesen exakten Artikel formuliert.
gleiche_bedingung_und_wertartYesDruck, Strahlart und Höchstwert oder Einzelwert sind in beiden Angaben gleich dokumentiert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/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 only a semantic framing of comparing scopes; it does not explain decision criteria, determinism, failure cases, or what the tool actually does with the five inputs. It does not contradict the annotations, but it adds little behavioral context beyond them.

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?

The description is short and front-loaded, stating the German task before the English gloss. The bilingual duplication is not wasteful for a German-named tool, though the wording remains abstract rather than crisp.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, all-required resolution tool with no output schema, the description is too thin. It does not explain how the inputs are combined, what a successful resolution looks like, or what result the caller receives, leaving important context undocumented.

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%, and each of the five required parameters is documented in the schema. The description adds no further parameter semantics, such as how the boolean checks combine or what constitutes a match, so the schema carries the parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the two things being separated (Serienhöchstwert/showroom headline vs. technische Artikelzeile/exact technical row) and mentions scope, but the verb 'auseinanderhalten'/'resolve' leaves the actual operation ambiguous. It does not clearly state whether the tool decides equality, returns a classification, or performs some other resolution, and it gives no sibling differentiation.

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?

There is no explicit when-to-use, when-not-to-use, or alternative guidance. The scope language hints at the task, but the agent is not told what condition should select this tool over the many similar brause/zuordnen siblings.

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