Skip to main content
Glama

getecoback-climate-weather

luftbefeuchter_nachfuellen_kleine_portionen

Read-only

Nachfüllportionen mit einem vorhandenen kleinen Gefäß planen — Calculate hand-carried refill portions when the device instructions permit in-place filling.

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": {
      "nachfuellmenge_ml": "<nachfuellmenge_ml>",
      "gefaess_ml": "<gefaess_ml>",
      "vor_ort_freigegeben": "<vor_ort_freigegeben>"
    },
    "name": "luftbefeuchter_nachfuellen_kleine_portionen"
  }
}

Input Schema

NameRequiredDescriptionDefault
gefaess_mlYesTatsächlich gewählte Füllmenge je Gefäß in ganzen ml.
nachfuellmenge_mlYesBeabsichtigte Nachfüllmenge unterhalb der Markierung in ganzen ml.
vor_ort_freigegebenYesErlaubt die Anleitung der genauen Variante das Befüllen am vorgesehenen Standort?

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 calculation. The description adds useful context that it is a planning/calculation tool governed by whether in-place filling is permitted, but it does not explain what happens when that permission is false or what result is produced.

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 definition is a single, front-loaded sentence with no wasted wording. The bilingual phrasing is slightly awkward but still efficient and easy to parse.

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 three fully described required inputs and a read-only annotation, the description is adequate for calling the tool. However, for a calculation tool with no output schema, it does not describe the kind of result the agent should expect, such as portions, leftover amounts, or feasibility.

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?

The input schema has 100% description coverage, so the three parameters are already well documented. The description adds contextual meaning around 'hand-carried' portions and the in-place permission condition, but does not provide additional parameter-level semantics beyond the schema.

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 uses a specific verb ('planen' / 'Calculate') and resource ('Nachfüllportionen' / 'refill portions'), and adds the condition of using an existing small vessel. It is clear what the tool computes, though it does not explicitly distinguish itself from any sibling tool.

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?

It states the key usage condition: hand-carried refill portions are calculated when device instructions permit in-place filling. It does not mention when not to use the tool, prerequisites beyond that condition, or an alternative sibling tool.

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