Skip to main content
Glama

getecoback-raumklima

beurer_ks34_aaa_batteriesatz_mix_abgleichen

Read-only

Batteriesatz der KS 34 70311 mit der Typvorgabe und dem Herstellerhinweis zum Mischen abgleichen — Check the documented cell count, type and matched-battery condition.

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": {
      "modell_belegt": "<modell_belegt>",
      "typ": "<typ>",
      "anzahl": "<anzahl>",
      "mischung": "<mischung>"
    },
    "name": "beurer_ks34_aaa_batteriesatz_mix_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
typYesTatsächlicher Typ laut Beschriftung.
anzahlYesVorgesehene Anzahl Zellen.
mischungYesSind Typen, Hersteller oder alte und neue Zellen gemischt?
modell_belegtYesDie deutsche Ausführung KS 34 XL Black 70311 ist am konkreten Gerät belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint=true and openWorldHint=false annotations already tell the agent this is a side-effect-free, closed-domain check, so the description's main added value is that it validates against a documented spec rather than performing any change. It does not say what a failed reconciliation produces or whether any verdict/state is recorded, and there is no output schema to fill that gap.

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 gets to the resource and the checked properties immediately, with the English half acting as a clarifying gloss. The bilingual duplication is mild redundancy but not wasteful enough to hurt.

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?

All four required parameters are fully documented in the schema and the tool is read-only, so an agent can call it correctly. However, with no output schema the description should ideally indicate what the reconciliation returns (match/mismatch verdict, which condition failed), which it omits.

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 description coverage is 100% with two enums, so the schema already carries the semantics and the baseline is 3. The description echoes three of the four parameters (Anzahl, Typ, Mischung) but adds no formats, ranges or edge-case meaning beyond the schema, and never mentions modell_belegt.

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 (abgleichen/reconcile) and resource (Batteriesatz der KS 34 70311) and enumerates the three things being checked: cell count, type and matched-battery condition. That is clearly more informative than the title-less name alone, though it never distinguishes itself from the many sibling KS 34 topic checks.

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: the agent can infer this is the tool for validating a battery set against the documented spec rather than, say, cleaning or weighing-capacity questions. There is no explicit statement of when to call it versus a sibling, and no prerequisites or exclusions are given.

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