Skip to main content
Glama

getecoback-raumklima

gebrauchtgeraet_mehrfachbeigabe_ohne_gebrauchsnachweis

Read-only

Bei als neu beiliegenden Verbrauchsteilen belegte und offene Mengen von bereits eingebauten Teilen abgrenzen — Audit unverified extras without treating them as usable spares.

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": {
      "gleiche_varianten_belegt": "<gleiche_varianten_belegt>",
      "extras_vorhanden": "<extras_vorhanden>",
      "geoeffnet_oder_benutzt": "<geoeffnet_oder_benutzt>",
      "intakt_belegt": "<intakt_belegt>",
      "eingebaut_gezaehlt": "<eingebaut_gezaehlt>"
    },
    "name": "gebrauchtgeraet_mehrfachbeigabe_ohne_gebrauchsnachweis"
  }
}

Input Schema

NameRequiredDescriptionDefault
intakt_belegtYesDavon getrennt belegbar unbenutzt und original verpackt.
extras_vorhandenYesZusätzlich physisch beiliegende Einzelteile.
eingebaut_gezaehltYesBereits eingebaute Teile, die separat aufgeführt sind.
geoeffnet_oder_benutztYesDavon sichtbar geöffnet oder in Benutzung protokolliert.
gleiche_varianten_belegtYesSind Grundteil und einzelne beigelegte Verbrauchsteile dem angebotenen Exemplar korrekt zugeordnet?

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 an agent knows this is a safe, closed-domain read. The description adds a meaningful behavioural stance – extras are audited but not reclassified as usable spares – which goes somewhat beyond the annotations. It still does not say what kind of result is produced (a reconciliation figure, a flag, an error on mismatch), which matters for a computation-style tool.

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 German sentence plus a short English gloss – front-loaded with the core operation and with no padding. The phrasing is convoluted ('Bei als neu beiliegenden Verbrauchsteilen belegte und offene Mengen ... abgrenzen'), which costs a little readability but nothing is wasted.

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?

Five required numeric/boolean inputs are fully documented in the schema and the safety profile is covered by annotations. The main gap is that there is no output schema and the description does not indicate what the tool returns, so an agent cannot anticipate the result shape of this reconciliation step.

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% and every parameter carries a German description, so the baseline is 3. The description does add a modest framing by pointing at the tension between documented quantities and 'bereits eingebauten Teilen', which helps orient the five required figures. It does not, however, explain how the boolean 'gleiche_varianten_belegt' gate interacts with the count fields.

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: separating documented ('belegte') from open/unverified quantities of consumable parts that were declared as newly included, and cross-checking them against already-installed parts. That is a specific verb-plus-resource rather than a restatement of the name. It is dense domain jargon and does not contrast itself with any of the many sibling 'gebrauchtgeraet_*' tools, which keeps it from a 5.

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 phrase 'Audit unverified extras without treating them as usable spares' conveys the intent and implicitly the situation in which the tool applies (extras lacking proof of use). However, no explicit when-to-use/when-not-to-use conditions, prerequisites, or alternative tools are named. Usage must be inferred from the goal statement.

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