Skip to main content
Glama

getecoback-raumklima

thermostat_wechselakku_ladefenster

Read-only

Bei abnehmbaren Herstellerakkus die gleichzeitig zu ladenden Packs und die Gesamtzeit planen — Plan charging batches for a verified removable thermostat battery pack.

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": {
      "akkus": "<akkus>",
      "ladeplaetze": "<ladeplaetze>",
      "ladezeit_pro_runde_min": "<ladezeit_pro_runde_min>",
      "abnehmbar_bestaetigt": "<abnehmbar_bestaetigt>"
    },
    "name": "thermostat_wechselakku_ladefenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
akkusYesAnzahl der gerade zum Laden vorgesehenen gleichen Hersteller-Akkus.
ladeplaetzeYesAnzahl gleichzeitig nutzbarer dokumentierter Ladeplätze.
abnehmbar_bestaetigtYesGenaues Modell, abnehmbare Packs und zulässiges Ladeverfahren sind bestätigt?
ladezeit_pro_runde_minYesEigene beobachtete Dauer je Charge in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safe, closed-world computation profile is covered by structured data. The description adds only the "verified removable pack" precondition, which largely duplicates the required abnehmbar_bestaetigt boolean, and says nothing about how batches are formed or what the plan output looks like.

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 pair with no filler; the German line carries the specifics and the English line is a compact restatement rather than padding. Slight redundancy from the bilingual duplication keeps it off a 5.

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 simple four-parameter calculation with full schema documentation and safety annotations, the definition is minimally sufficient. The notable gap is the absence of any statement about the returned plan or total time, which is the tool's whole point since no output schema exists.

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% and each of the four parameters is documented in the schema, so the baseline is 3. The description's mention of simultaneous packs and total time loosely maps to akkus/ladeplaetze and ladezeit_pro_runde_min but adds no format, unit, or edge-case guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a resource and an activity ("gleichzeitig zu ladenden Packs und die Gesamtzeit planen"), which is more than a restatement of the name. But "planen" is soft: it never states whether the tool computes a schedule, returns a total duration, or just validates inputs, and it draws no explicit line against the many other thermostat_* planning siblings.

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 by the precondition "Bei abnehmbaren Herstellerakkus" and by the required confirmation flag, so an agent can infer the gate. There is no explicit when-to-use/when-not statement and no named alternative among the sibling tools, leaving routing to inference.

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