Skip to main content
Glama

getecoback-climate-weather

brause_strahlarten_anzeigename_zuordnungsbeleg

Read-only

Bei zwei ähnlichen Strahlnamen die tatsächlich bezeichnete Auswahl vor einem Angebotsvergleich prüfen — Check which exact spray name belongs to the observed selector.

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": {
      "anleitung_strahlname": "<anleitung_strahlname>",
      "anzeige_vollstaendig": "<anzeige_vollstaendig>",
      "zuordnung": "<zuordnung>",
      "identischer_artikel": "<identischer_artikel>"
    },
    "name": "brause_strahlarten_anzeigename_zuordnungsbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
zuordnungYesSicht- oder Textabgleich der Strahlart.
identischer_artikelYesAuswahlzustand und Anleitung gehören zum selben exakten Artikel.
anleitung_strahlnameYesDer vollständige offizielle Name und die zugehörige Auswahl sind dokumentiert.
anzeige_vollstaendigYesBeim tatsächlichen Auswahlzustand ist der ganze Name oder ein eindeutig erklärtes Symbol erfasst.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 this is a verification step gating an offer comparison, but says nothing about what a returned judgment looks like or how conflicts (e.g. 'offen') should be treated.

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?

A single front-loaded sentence that puts the condition before the action, followed by a compact English rendering. The bilingual duplication is mildly redundant but not wasteful given the ambiguous German compound name.

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

Completeness4/5

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

With four fully documented required parameters, no output schema, and read-only annotations, the description supplies the missing decision context: what the evidence is for. Only the meaning of the recorded booleans in relation to the verdict is left implicit.

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% with per-field German descriptions and an enum for zuordnung, so the schema carries the parameter burden. The description only loosely echoes the idea of an exact match ('tatsächlich bezeichnete Auswahl', 'exakt'), adding no syntax or decision rules beyond the schema.

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 gives a concrete verb-plus-object: check which exact spray name belongs to the observed selector, resolved via the recorded assignment evidence. It is far clearer than the opaque compound name, though it only hints at differentiation from the sibling offer-comparison tools rather than naming them.

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?

It states the trigger condition (two similar spray names) and the workflow position (before an offer comparison), which tells an agent when this tool is appropriate. It stops short of naming alternatives or stating when not to use it.

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