Skip to main content
Glama

getecoback-raumklima

feuchteprotokoll_raumwechsel_logbuch_abdeckung

Read-only

Ermittle, wie viel einer Messreihe nach einem Recorderwechsel noch auf denselben Messort zurückgeführt werden kann — Quantify location-resolved evidence after switching room loggers

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": {
      "gesamtzahl": "<gesamtzahl>",
      "vor_wechsel_eindeutig": "<vor_wechsel_eindeutig>",
      "nach_wechsel_eindeutig": "<nach_wechsel_eindeutig>",
      "doppelt_importiert": "<doppelt_importiert>"
    },
    "name": "feuchteprotokoll_raumwechsel_logbuch_abdeckung"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamtzahlYesAnzahl aller Ablesungen im übernommenen Protokoll
doppelt_importiertYesZusätzlich als doppelt erkannte Protokolleinträge außerhalb der beiden Teilmengen
vor_wechsel_eindeutigYesAblesungen vor dem Wechsel mit eindeutig markiertem Messort
nach_wechsel_eindeutigYesWeitere Ablesungen nach dem Wechsel mit dem gleichen eindeutig markierten Messort

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 establish this as a read-only, closed-world operation, so the bar is lower, but the description adds little beyond that: it doesn't reveal how the four supplied counts are combined, how duplicate imports are treated relative to the two subsets, or what happens when gesamtzahl is zero. With no output schema, the description is the only place the returned metric could be characterised, and it is silent on that.

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 sentence with the verb front-loaded, preceded by a German formulation and followed by an English gloss; no filler. The bilingual duplication costs a little length but serves clarity rather than padding.

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?

The tool is a simple pure computation with four fully documented required parameters, which the definition handles adequately. However, without an output schema, the definition leaves the result's meaning (fraction of evidence retained vs. absolute counts) unstated, which is the main thing an agent would need in order to use the answer correctly.

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%, with each of the four numeric parameters documented in German including bounds, so the schema carries the parameter burden. The description adds no interpretation of the parameters (e.g. whether vor_wechsel_eindeutig and nach_wechsel_eindeutig must be disjoint from doppelt_importiert), 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 (quantify / 'Ermittle') and a specific resource: how much of a measurement series remains attributable to the same measurement location after a room-logger (recorder) change. It is clearly distinct from siblings like entfeuchter_raumwechsel_tankrest_zuteilen. It does not say what form the answer takes (a ratio, a percentage, a residual count), which keeps it short of a 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 when-to-use or when-not-to-use guidance, no prerequisites, and no reference to any alternative tool, even though several sibling names involve Raumwechsel attribution. An agent must infer the applicability of this tool entirely from the one-line purpose.

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