Skip to main content
Glama

getecoback-climate-weather

kundenrezension_modellgruppe_pruefen

Read-only

Bewertungen aus einer gemeinsamen Händlerseite dem richtigen Modell zuordnen — Assess whether a retailer review count applies to the exact variant.

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": {
      "gesamt": "<gesamt>",
      "gefiltert": "<gefiltert>",
      "filter_geprueft": "<filter_geprueft>"
    },
    "name": "kundenrezension_modellgruppe_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamtYesSichtbare Anzahl Bewertungen für die gesamte Angebotsgruppe.
gefiltertYesSichtbare Anzahl nach bestätigtem Modellfilter; bei fehlendem Filter 0.
filter_geprueftYesHändler bestätigt den Filter für genau die Modellvariante?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 safety is covered. The description adds that this is a plausibility assignment of review counts to variants, but does not disclose how the three inputs combine into a verdict or what the result communicates (no output schema exists).

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 with no wasted preamble. The bilingual repetition (German plus English gloss) is redundant but does aid cross-language comprehension, so it is not pure padding.

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 read-only three-parameter check with fully documented parameters and no output schema, the description covers the intent but omits the decision rule and the shape of the verdict. An agent can call it but cannot predict what true/false configuration produces which conclusion.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear German descriptions for gesamt, gefiltert and filter_geprueft, so the baseline would be 3. The description's framing ('whether a review count applies to the exact variant') contextualizes what the parameters are being tested against, adding modest meaning 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 names a concrete operation (assigning/checking retailer review counts against the correct model variant), which is more specific than the bare tool name. It is bilingual and partly abstract ('dem richtigen Modell zuordnen'), so an agent understands the domain but not precisely what is checked or returned.

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 phrasing 'Bewertungen aus einer gemeinsamen Händlerseite' implies the situation (review counts on a shared retailer listing page may belong to a different variant), giving implied usage. There is no explicit when-to-use/when-not guidance or named alternative among the many sibling '_pruefen' tools.

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