Skip to main content
Glama

getecoback-raumklima

kuehltechnik_varianten_beleg_inverter

Read-only

Ob eine behauptete Leistungsregelung wirklich für die angebotene Klimageräte-Variante beschrieben ist, von Formfaktor und Werbewort trennen — Qualify evidence for inverter modulation without inferring it from split versus monoblock.

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": {
      "angebotsform": "<angebotsform>",
      "modell_gleich": "<modell_gleich>",
      "beschreibung": "<beschreibung>"
    },
    "name": "kuehltechnik_varianten_beleg_inverter"
  }
}

Input Schema

NameRequiredDescriptionDefault
angebotsformYesBauform des angebotenen Geräts.
beschreibungYesWortlaut der technischen Unterlage.
modell_gleichYesGilt das technische Dokument genau für den angebotenen Artikel und Markt?

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 the safety profile is known. The description adds a genuine behavioral constraint — that the form factor must not be used as evidence — which is useful context beyond the annotations. It says nothing about how the qualification is returned or what distinguishes a positive from a negative finding.

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?

Effectively one dense sentence that front-loads the qualification task and then the separation constraint. No filler, though the German/English mix makes it slightly harder to parse than a single-language statement would be.

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?

Three small required parameters, all documented, no nested objects, no output schema to explain. The description covers the judgment the tool performs and its main pitfall, which is nearly everything an agent needs. Only the nature of the returned qualification 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% and both enum parameters carry their own descriptions, so the schema carries the parameter burden. The description only maps loosely onto angebotsform and beschreibung via 'Formfaktor und Werbewort' and adds no format or interpretation detail. Baseline 3 is appropriate.

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 act — qualifying whether inverter modulation is actually documented for the offered unit variant — and explicitly separates that claim from form factor (split vs monoblock) and marketing wording. That is more than a restatement of the name. It stops short of naming a sibling tool to contrast against, so it is clear but not fully differentiated.

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?

Usage is implied rather than stated: an agent can infer it applies when a claimed Leistungsregelung must be verified against the technical document. The one exclusion present is about reasoning ('without inferring it from split versus monoblock'), not about when to pick a different tool. No alternative or prerequisite is named.

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