Skip to main content
Glama

getecoback-climate-weather

entfeuchter_tankereignis_protokoll_zweistand

Read-only

Tankstände vor und nach einem bestätigten Ereignis auf getrennte Füllabschnitte prüfen — Distinguish continued fill from logged emptying between two readings.

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_l": "<vorher_l>",
      "nachher_l": "<nachher_l>",
      "messintervall_zustand": "<messintervall_zustand>",
      "ausgeleert_l": "<ausgeleert_l>"
    },
    "name": "entfeuchter_tankereignis_protokoll_zweistand"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorher_lYesErster gelesener Tankstand im selben Gerät.
nachher_lYesSpäterer gelesener Stand im selben Tank.
ausgeleert_lYesBei vollständig gemessenen Leerungen insgesamt erfasste Liter. Bei bestätigter Nichtleerung 0.
messintervall_zustandYesBekannter Zustand zwischen den Messungen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 safety and scope are covered and the description does not contradict them. The description adds interpretive context (that the result separates fill from emptying) but says nothing about what is returned, how the 'unklar' interval state is handled, or how partial versus complete emptying is treated beyond the schema wording.

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?

The definition is short and front-loads the operation, but the em-dash construction restates the same idea twice in German and English without the second phrasing adding precision. 'Auf getrennte Füllabschnitte prüfen' is dense and ambiguous rather than economical.

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 required numeric/enum parameters and no output schema, the description should clarify what verdict is produced (for example, whether the result is a classification of continued fill versus emptying). It gestures at the distinction but leaves the returned judgment and the handling of edge cases underspecified.

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 are already documented, including the enum for messintervall_zustand and the meaning of ausgeleert_l=0. The description's 'vor und nach' and 'logged emptying' framing corroborates but does not extend that meaning, so the baseline of 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 concrete operation: comparing tank levels before and after a confirmed event and attributing them to separate fill segments, in order to distinguish continued filling from a logged emptying. That is a specific verb-plus-resource, not a restatement of the name. It does not, however, distinguish itself from close siblings such as entfeuchter_tankleerung_zwei_zeitpunkte or entfeuchter_tankleerungen_zeitbilanz.

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 through the phrase 'bestätigten Ereignis' – the agent can infer this applies when an event is already confirmed – but there is no explicit when-to-use rule, no exclusion, and no pointer to which sibling handles the unconfirmed or single-reading case. The agent must infer routing from the name alone.

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