Skip to main content
Glama

getecoback-climate-weather

entfeuchter_tankleerung_zwei_zeitpunkte

Read-only

Eine Tankleerung zwischen zwei beaufsichtigten Messabschnitten so einplanen, dass der eigene beobachtete Bedarf passt. — Check one manual tank emptying between two supervised dehumidifier sessions.

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": {
      "anfangsfrei_ml": "<anfangsfrei_ml>",
      "tank_frei_nach_leeren_ml": "<tank_frei_nach_leeren_ml>",
      "sammlung_a_ml": "<sammlung_a_ml>",
      "sammlung_b_ml": "<sammlung_b_ml>",
      "leerung_zwischenzeit": "<leerung_zwischenzeit>"
    },
    "name": "entfeuchter_tankleerung_zwei_zeitpunkte"
  }
}

Input Schema

NameRequiredDescriptionDefault
sammlung_a_mlYesBei vergleichbarer Temperatur und Feuchte beobachtete Sammelmenge im ersten Abschnitt.
sammlung_b_mlYesEbenso beobachtete Sammelmenge im zweiten Abschnitt.
anfangsfrei_mlYesZu Beginn praktisch freier Tankinhalt bis zum dokumentierten Füllstopp.
leerung_zwischenzeitYesIst eine Person zwischen beiden Abschnitten für die Tankleerung verfügbar?
tank_frei_nach_leeren_mlYesPraktisch freier Tankinhalt direkt nach vorgabegerechtem vollständigen Entleeren.

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?

The readOnlyHint and openWorldHint annotations already establish that this is a safe, closed-world read/calculation operation. The description adds that the task concerns a manual emptying between supervised sessions and should fit observed demand, but it does not explain whether the result is an advisory schedule, a feasibility check, or a computed interval. It also does not clarify how the availability boolean affects the outcome.

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?

The description is short and front-loaded, stating the task in one German sentence followed by an English translation. The bilingual duplication is somewhat redundant but does not obscure the core action. Every sentence relates directly to the tool's purpose.

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?

Given five required parameters and no output schema, the description is adequate for identifying the task but incomplete about the expected result. An agent can understand what inputs are needed from the schema, but the description does not say whether the tool returns a schedule, a yes/no feasibility answer, or a recommended emptying time. For a calculation-style tool with no output schema, that is a meaningful gap.

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 all five parameters are individually documented with German descriptions. The main description adds little parameter-specific meaning beyond the schema; it frames the overall task but does not explain how sammlung_a_ml, sammlung_b_ml, or leerung_zwischenzeit are used in the calculation. A baseline 3 is appropriate because the schema carries the parameter semantics.

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 specific verb and resource: planning/checking one manual tank emptying between two supervised dehumidifier measurement sections. It also adds the goal of matching the user's observed demand, which helps distinguish it from generic tank checks. It does not explicitly differentiate itself from similar siblings such as entfeuchter_tank_leerintervall 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?

The description implies the use case: scheduling a single tank emptying between two supervised measurement periods. However, it gives no explicit when-to-use or when-not-to-use guidance and does not name any sibling alternative for related tank calculations. The condition is inferable but not fully specified.

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