Skip to main content
Glama

getecoback-raumklima

kaercher_wd418_laufzeit_testakku_scope

Read-only

Prüfe, ob die publizierte WD-4-18-Laufzeit auf den nachgewiesenen Akkusatz bezogen ist — Verify the documented WD 4-18 runtime battery configuration

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": {
      "set_16286010": "<set_16286010>",
      "akku_a_ah": "<akku_a_ah>",
      "akku_b_ah": "<akku_b_ah>",
      "kompatibler_satz_belegt": "<kompatibler_satz_belegt>",
      "eigener_bedarf_min": "<eigener_bedarf_min>"
    },
    "name": "kaercher_wd418_laufzeit_testakku_scope"
  }
}

Input Schema

NameRequiredDescriptionDefault
akku_a_ahYesAufgedruckte Kapazität des ersten bestätigten kompatiblen Akkus in Ah
akku_b_ahYesAufgedruckte Kapazität des zweiten bestätigten kompatiblen Akkus in Ah
set_16286010YesDokumentiertes Set 1.628-601.0 mit genauer Variantenkennung bestätigt
eigener_bedarf_minYesBenötigte aktive Minuten für die eigene Aufgabe
kompatibler_satz_belegtYesZwei kompatible 18-V-Akkus im konkreten Paket bestätigt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 no behavioral context beyond the purpose sentence: it does not say what the verification produces, whether it compares capacity against the runtime claim, or what constitutes a positive outcome for a tool with five mandatory inputs and no output schema.

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 verb first, plus a compact English gloss. The bilingual restatement is slightly redundant but short enough not to waste space.

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?

For a tool with five required parameters, no output schema, and no explanation of the verification logic, the description is thin. It never explains what the runtime claim is being checked against or what the agent should expect back, leaving a meaningful gap for a non-trivial evaluation tool.

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%, so all five parameters (set_16286010, akku_a_ah, akku_b_ah, kompatibler_satz_belegt, eigener_bedarf_min) are already documented in the schema with ranges and meanings. The description adds no additional semantics such as how the two capacities or the required minutes are combined, so the baseline 3 applies.

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 (prüfen/verify) and a specific resource (the published WD 4-18 runtime in relation to the documented battery set), so an agent can tell it is a claim-scoping check rather than a generic lookup. It does not differentiate itself from any of the many sibling verification tools, which is the gap keeping it below 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when this check applies versus alternatives, no prerequisites, and no exclusions. The agent must infer from the description alone that this is only for cases where a runtime figure and a documented battery set both exist.

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