Skip to main content
Glama

getecoback-raumklima

kuehltechnik_beleg_raumtemperatur_empfindung

Read-only

Einen dokumentierten Kühleffekt als Raumwert, lokale Lufttemperatur oder Empfindung beschriften — Clarify what the reported cooling endpoint actually describes.

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": {
      "endpunkt": "<endpunkt>",
      "referenz_gleich": "<referenz_gleich>",
      "temperaturabfall_c": "<temperaturabfall_c>"
    },
    "name": "kuehltechnik_beleg_raumtemperatur_empfindung"
  }
}

Input Schema

NameRequiredDescriptionDefault
endpunktYesIm Prüfbeleg erfasste Zielgröße.
referenz_gleichYesVergleichsbedingungen, Dauer und Messort stimmen überein?
temperaturabfall_cYesDokumentierter Abfall in Grad Celsius; 0 falls kein Temperaturwert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safety is covered. The description adds nothing about behavior: it does not say whether a result is just a classification of existing data, what happens when referenz_gleich is false, or whether the operation validates the documented value. "Beschriften" (label) is mildly at odds with the read-only framing but is plausibly meant as 'interpret', so this is ambiguity rather than a contradiction.

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?

Two compact clauses with the goal front-loaded and a clarifying English sentence that resolves the German phrasing. The bilingual restatement is slightly redundant but not wasteful.

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 three-required-parameter classification tool with full schema coverage and read-only annotations, the essentials are present. However, with no output schema, the description never indicates what the agent receives back (a classified endpoint? a validation verdict?), which is a real gap for a tool whose whole job is disambiguation.

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 schema already documents all three parameters and their bounds. The description's mention of "Raumwert, lokale Lufttemperatur oder Empfindung" loosely mirrors the endpunkt enum but adds no rule for choosing among values, and referenz_gleich and temperaturabfall_c are not elaborated at all. 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 states a concrete action ("beschriften" / clarify) applied to a specific resource: the cooling endpoint reported in a test record, enumerating the candidate meanings (room value, local air temperature, sensation). The English gloss "Clarify what the reported cooling endpoint actually describes" makes the intent unambiguous despite the opaque tool name. It stops short of differentiating itself from siblings such as kuehltechnik_varianten_beleg_inverter.

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: an agent can infer the tool fits when a documented temperature drop has an ambiguous measurement basis. There is no explicit when-to-use, no when-not-to-use, and no named alternative for cases where the endpoint is already known.

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