Skip to main content
Glama

getecoback-raumklima

rollwagen_fuellzustand_und_tatsache_fahrtbeleg

Read-only

Prüft, ob eine beobachtete Fahrt und die genaue Unterlage denselben Befüllzustand abdecken — Check the water-fill state in the actual observation and applicable documentation.

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": {
      "ziel": "<ziel>",
      "beobachtet": "<beobachtet>",
      "dokument": "<dokument>",
      "fuellmenge_beobachtet": "<fuellmenge_beobachtet>"
    },
    "name": "rollwagen_fuellzustand_und_tatsache_fahrtbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
zielYesBelegter Zustand des später betrachteten Aufbaus.
dokumentYesWelcher Zustand wird in den passenden Unterlagen erläutert?
beobachtetYesZustand der konkreten vorliegenden Beobachtung.
fuellmenge_beobachtetYesBei zwei befüllten Zuständen ist die beobachtete Füllmenge mit dem Zielzustand vergleichbar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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. Beyond that the description adds only "it checks" — it does not say what the check yields (a boolean verdict? a mismatch report?), what happens when inputs are "offen" or "beide", or how conflicts between ziel, beobachtet and dokument are resolved. For a verdict-producing tool with no output schema, that is a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but roughly half the text is a German/English restatement of the same clause rather than new information, and the English half ("water-fill state") is narrower and less accurate than the German. Front-loading the comparison logic rather than a translation would have been better use of the space.

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 with intertwined enum states (leer/befuellt/offen/beide) and a conditional boolean demand at least a sentence on how they combine to produce a verdict, and there is no output schema to fall back on. The description never explains that combination logic, so an agent knows the topic but not how to interpret the result.

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 including the enum meanings and the fuellmenge_beobachtet boolean are already documented in the schema; baseline 3 applies. The description names the concepts (observation, documentation, fill state) but adds no syntax, default, or interaction semantics beyond the schema.

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?

"Prüft, ob ... denselben Befüllzustand abdecken" gives a concrete verb (checks agreement) and a concrete resource (fill state across observation vs. documentation), which is more than a restatement of the name. However, the interleaved "beobachtete Fahrt" (observed trip) introduces a concept that appears nowhere in the parameters and muddies what exactly is being compared, and nothing distinguishes this check from the many similarly named rollwagen/beleg tools.

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 statement of when this check should be run, no prerequisites, and no pointer to an alternative (e.g. a pure documentation lookup or a pure observation tool). The agent must infer from the name alone that this is a consistency-audit step.

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