Skip to main content
Glama

getecoback-raumklima

gebrauchtgeraet_testlauf_vorherige_befuellung_effekt

Read-only

In einer Entfeuchter-Vorführung bereits vorhandenes Tankwasser vom gemessenen Zuwachs trennen — Correct a used-unit demonstration for pre-existing tank contents.

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": {
      "messung_durchgehend": "<messung_durchgehend>",
      "vorher_ml": "<vorher_ml>",
      "nachher_ml": "<nachher_ml>",
      "messspanne_ml": "<messspanne_ml>"
    },
    "name": "gebrauchtgeraet_testlauf_vorherige_befuellung_effekt"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorher_mlYesIm Tank vor Vorführung dokumentierte Menge, in ml.
nachher_mlYesIm Tank am Ende dokumentierte Menge, in ml.
messspanne_mlYesGemeinsame Ableseunsicherheit, in ml.
messung_durchgehendYesSind beide Ablesungen in derselben normalen beobachteten Betriebsphase mit unverändertem Tank und ohne Zugabe erfolgt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/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 and the bar is lower. The description adds the purpose-level behavior (netting out pre-existing water) but says nothing about how the shared measurement uncertainty parameter affects the result or what the corrected figure represents, which matters for a computation tool with no output schema.

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 short clauses, front-loaded with the scenario and the operation, with no filler. The bilingual restatement is slightly redundant but cheap and aids disambiguation, so the text is efficient overall.

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?

With four fully documented required parameters, a closed schema, and read-only annotations, most of what an agent needs is present. However, since no output schema exists, the description should indicate what comes back (a corrected growth value, a boolean, or a pass/fail on the continuity condition) and it does not.

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 every parameter carries a German description with bounds, so the schema does the heavy lifting. The description adds no extra meaning about the before/after readings, the shared uncertainty, or the continuity flag beyond what the schema already states; 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 verb and object: separating pre-existing tank water from the measured increase in a used-unit dehumidifier demonstration, plus an English restatement. The scenario is narrow and specific enough to distinguish it from the many inspection/evidence siblings, though it never names a sibling tool or the adjacent case it is not.

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 context (Entfeuchter-Vorführung with pre-existing tank contents) implicitly tells the agent when this applies, but there is no explicit when-not guidance, no prerequisites, and no named alternative for the case where the tank was empty or the reading was not continuous. Usage is inferable rather than stated.

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