Skip to main content
Glama

getecoback-climate-weather

elektrog_kleingeraete_dreifach_mass_anzahl

Read-only

Eine dokumentierte Geräteart anhand ihrer größten äußeren Abmessung und der Zahl im selben Vorhaben mit der 0:1-Regel abgleichen — Check the inclusive size threshold and the per-type small-device count together.

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": {
      "a_cm": "<a_cm>",
      "b_cm": "<b_cm>",
      "c_cm": "<c_cm>",
      "spielraum_cm": "<spielraum_cm>",
      "stueck_gleiche_art": "<stueck_gleiche_art>",
      "gleiche_bauform_und_art_belegt": "<gleiche_bauform_und_art_belegt>"
    },
    "name": "elektrog_kleingeraete_dreifach_mass_anzahl"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_cmYesErste äußere Abmessung des betrachteten Altgeräts in Zentimetern.
b_cmYesZweite äußere Abmessung in Zentimetern.
c_cmYesDritte äußere Abmessung in Zentimetern.
spielraum_cmYesBegründete maximale absolute Abweichung je Abmessung. Exakten Beleg mit 0 kennzeichnen.
stueck_gleiche_artYesAnzahl gleichartig bestätigter Altgeräte im selben Vorhaben. Die gemessenen Maße gelten für alle hier gezählten Stücke.
gleiche_bauform_und_art_belegtYesÄußere Abmessungen und genau dieselbe Geräteart aller gezählten Stücke sind belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so safety is covered, but the description contributes little: the core rule ("0:1-Regel") is never defined, nor is what a positive/negative reconciliation means, what boundary applies, or what the caller gets back. Only 'inclusive size threshold' hints at behaviour.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence pair, reasonably front-loaded, but the German/English duplication adds no information and the jargon density wastes the space that should explain the rule.

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?

Six required parameters, no output schema, and the decision logic is left opaque. For a rule-checking tool the description should state the rule and the verdict, and it does neither, so an agent cannot predict the result of a call.

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 the baseline is 3. The description adds a small nudge by implying the largest outer dimension drives the threshold and that the count applies to the same Vorhaben, but it does not clarify how spielraum_cm or gleiche_bauform_und_art_belegt interact with the 0:1 rule.

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 verb (abgleichen) and a resource (a documented device type), but the operative criterion is an unexplained term, "0:1-Regel", and the second sentence only restates 'check the size threshold and the count together'. It never says plainly what the tool returns or decides, and gives no contrast with the many elektrog_* siblings.

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?

No when-to-use guidance, no preconditions, and no mention of when another tool (e.g. a pure measurement or a per-category classifier) would be the right choice instead. The agent must infer applicability from the parameter list alone.

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