Skip to main content
Glama

getecoback-raumklima

pinguino_typnummer_kuehlleistung_nachweisgrenze

Read-only

Prüfe, ob eine Kühlleistung fälschlich aus der Pinguino-Typnummer abgeleitet wurde — Spot cooling capacity inferred from a Pinguino model code

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": {
      "behauptete_btuh": "<behauptete_btuh>",
      "beleg_btuh": "<beleg_btuh>",
      "genaue_variante": "<genaue_variante>",
      "aus_namenszahl": "<aus_namenszahl>"
    },
    "name": "pinguino_typnummer_kuehlleistung_nachweisgrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
beleg_btuhYesAuf dem exakten Datenblatt dokumentierte Leistung in BTU/h; 0 wenn unbekannt
aus_namenszahlYesDie Behauptung wurde rechnerisch aus einem Teil der Typnummer abgeleitet
behauptete_btuhYesZu prüfende behauptete Kühlleistung in BTU/h
genaue_varianteYesDas angezeigte Datenblatt stimmt mit der vollständigen Gerätebezeichnung überein

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 structurally. The description adds only the subject of the check, not what the check produces (verdict, reason, confidence), how conflicting evidence is resolved, or what happens when beleg_btuh is 0 (unknown).

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 clause with the checking target stated first; the bilingual echo adds length without contradiction and may aid matching. No filler sentences, though the English half is largely redundant.

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?

Four required parameters and no output schema mean the description must carry the burden of explaining the result, yet it never says what a call returns or how to read it. For a diagnostic/validation tool where the verdict is the whole point, this is a substantive gap.

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 four parameters are already documented in the schema, including the '0 wenn unbekannt' convention. The description adds no additional semantics about how these inputs interact (e.g. that genaue_variante gates the relevance of beleg_btuh), so the baseline 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 uses a specific verb ('Prüfe') plus a concrete object (whether a Kühlleistung was falsely derived from the Pinguino type number), which is far more than a restatement of the name. It implicitly separates itself from a plain unit-conversion sibling, but it never names an alternative, so an agent must infer the boundary.

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 it should call this when a BTU/h figure may have been computed from digits in a model code, as opposed to when the figure comes from a datasheet. There is no explicit when-to-use/when-not statement and no reference to sibling checks such as a unit reconciliation tool.

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