Skip to main content
Glama

getecoback-raumklima

feuchteaenderung_prozentpunkte_ausweisen

Read-only

Eine protokollierte Änderung relativer Raumfeuchte in Prozentpunkten korrekt beschriften — Distinguish relative humidity points from proportional changes and moisture removal.

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": {
      "vorher_rh": "<vorher_rh>",
      "nachher_rh": "<nachher_rh>",
      "temperatur_vorher_c": "<temperatur_vorher_c>",
      "temperatur_nachher_c": "<temperatur_nachher_c>"
    },
    "name": "feuchteaenderung_prozentpunkte_ausweisen"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorher_rhYesAbgelesene relative Feuchte vorher in Prozent.
nachher_rhYesAbgelesene relative Feuchte nachher in Prozent.
temperatur_vorher_cYesRaumtemperatur vorher in Grad Celsius.
temperatur_nachher_cYesRaumtemperatur nachher in Grad Celsius.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

The annotations already state readOnlyHint=true and openWorldHint=false, so its safety profile is already clear and the text does not need to repeat that. The description adds the framing that the change is "protokolliert" and that the output is a corrected designation, but it does not say what value or text is returned, whether warnings are raised for physically odd pairs, or how direction and magnitude are expressed. With the safety profile already covered, this description adds moderate value only.

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 compact statement with the core concept front-loaded and no filler; the bilingual em-dash construction is slightly jarring but does not waste words.

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?

There is no output schema, so the description carries the burden of telling the agent what comes back from four required numeric inputs, and it does not: no mention of a computed difference, a rendered label, rounding, or error behavior. For a small computational tool this is a notable gap, and the presence of required temperature inputs is left unexplained.

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 already carries a German description with bounds, so they are documented. However, the required temperature parameters are semantically unexplained for a mere percentage-point delta; the description could have said they exist to sanity-check absolute-humidity context, and it does not.

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 specific resource (a recorded change in relative room humidity expressed in percentage points) and a verb of sorts ("korrekt beschriften"), and it explicitly opposes percentage points to proportional change and to moisture removal. But it never says what the tool actually does operationally, whether it computes a delta, returns a label, or flags implausible input, so an agent cannot tell from the text alone what the call produces.

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?

The clause "Distinguish relative humidity points from proportional changes and moisture removal" implies the condition under which this tool is the right choice (percentage-point deltas, not percent-change or dehumidification calculations). That is genuine routing guidance, but it is conceptual, with no explicit when-not statement and no named alternative tool among the many humidity-related siblings.

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