Skip to main content
Glama

getecoback-raumklima

kueche_tropfablage_abgetrennte_auflagenprobe

Read-only

In einer kalten Abtropfprobe Wasser auf zwei Ablagen und tatsächlich in der Schale getrennt messen — Identify which observed surface contributed water outside the drip tray.

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": {
      "in_schale_ml": "<in_schale_ml>",
      "neben_a_ml": "<neben_a_ml>",
      "neben_b_ml": "<neben_b_ml>",
      "messung_alle_flaechen": "<messung_alle_flaechen>"
    },
    "name": "kueche_tropfablage_abgetrennte_auflagenprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
neben_a_mlYesDaneben auf Ablage A unabhängig aufgefangene Menge.
neben_b_mlYesDaneben auf Ablage B unabhängig aufgefangene Menge.
in_schale_mlYesGemessene Menge in der dafür vorgesehenen Auffangschale.
messung_alle_flaechenYesDie kalte Probe erfasste beide Ablagen und die Schale ohne Übertragung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint=true and openWorldHint=false annotations already cover the safety profile, and the description is consistent with them because this is a pure measurement or analysis operation. It does add one piece of genuinely useful information: the tool's purpose is to attribute water loss to a specific surface, which hints at the result. Still, it says nothing about how the probe is validated or what the result is shaped like.

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?

One compact sentence with a goal clause; nothing is redundant, and the action (separate measurement) is front-loaded before the goal (identifying the contributing surface). The convoluted German wording makes it slightly harder than necessary 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?

All four parameters are required and fully documented, and the goal clause gives an informal hint of what the tool determines. But there is no output schema and no statement of the return format: an agent cannot tell whether it gets a verdict, a per-surface volume, or both. For an analysis tool, 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%: all four parameters (in_schale_ml, neben_a_ml, neben_b_ml, messung_alle_flaechen) are documented in the schema, including ranges and the no-carryover condition. Since the description adds no format or interpretation detail beyond that, the 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?

States a specific verb and resource: separately measure water on two shelves (Ablagen) and in the drip tray, and determine which observed surface let water escape the tray. That is concrete enough to act on. However, the phrasing is dense and untranslated jargon ("kalte Abtropfprobe", "tatsächlich in der Schale"), and it never names how it differs from the many sibling measurement 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 explicit when-to-use or when-not-to-use guidance, and no alternative is named, even though the sibling list is full of similar separated-measurement tools. The experimental framing implies a context (a cold drip trial with separate collection), but an agent must infer that on its own.

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