Skip to main content
Glama

getecoback-raumklima

ersatzteil_softwarestand_angebot_abweichende_generation

Read-only

Ein dokumentiertes Software- oder Firmwareangebot nach Gerätestand und neuer Teileversion einordnen — Separate documented support for a variant from a generic software download.

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": {
      "geraetevariante": "<geraetevariante>",
      "hardwareteil": "<hardwareteil>",
      "offizieller_dienst": "<offizieller_dienst>",
      "angegebener_zugangsweg": "<angegebener_zugangsweg>"
    },
    "name": "ersatzteil_softwarestand_angebot_abweichende_generation"
  }
}

Input Schema

NameRequiredDescriptionDefault
hardwareteilYesBezug auf die tatsächlich angebotene Hardwarefassung.
geraetevarianteYesBezug auf die reparaturbezogene exakte Gerätevariante laut Anbieter.
offizieller_dienstYesQuelle wurde als zuständiger Hersteller- oder freigegebener Fachkanal nachgewiesen?
angegebener_zugangswegYesAusdrücklich genannter Zugang.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 nothing further about behavior: it does not say what evidence qualifies as "separate documented support", how conflicting or "offen" inputs are resolved, or what kind of assessment comes back.

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 the classification criterion stated first and the distinction second; the bilingual gloss is redundant but brief and does not obscure the point.

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?

With four required parameters, no output schema, and a judgement-style operation, the description should clarify what the assessment returns and how to act on "offen" values. It leaves the agent guessing about the result of the classification.

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 three enums carrying their own descriptions, so the schema does the heavy lifting and the baseline of 3 applies. The description contributes no additional meaning for geraetevariante, hardwareteil, offizieller_dienst or angegebener_zugangsweg.

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 verb ("einordnen") and object (a documented software/firmware offer) and adds a discriminating criterion: distinguishing documented support for a device variant from a generic software download. An agent can tell what the tool judges, though the phrasing is abstract and no sibling is named for contrast.

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 only implied: call it when you hold a documented software/firmware offer and must decide whether it covers the specific device variant. There is no explicit when-not, no prerequisites, and no named alternative among the many ersatzteil_* 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