Skip to main content
Glama

getecoback-climate-weather

spuelbecken_nutzungsuebergabe_abtropfzone

Read-only

Die bestätigte Nebenfläche zur Übergabe eines belegten Spülbeckens zeitlich einrechnen — Check whether a verified drip area keeps the sink available for its next use.

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": {
      "nass_ende": "<nass_ende>",
      "abtropf_min": "<abtropf_min>",
      "becken_faellig": "<becken_faellig>",
      "umsetzen_min": "<umsetzen_min>",
      "nebenflaeche_geprueft": "<nebenflaeche_geprueft>"
    },
    "name": "spuelbecken_nutzungsuebergabe_abtropfzone"
  }
}

Input Schema

NameRequiredDescriptionDefault
nass_endeYesEnde der ersten beobachteten Wasseraufgabe.
abtropf_minYesGewünschte Zeit bis zur nächsten Handhabung der Gegenstände.
umsetzen_minYesGemessene Zeit zum vollständigen Räumen des Beckens bei Nutzung der Nebenfläche.
becken_faelligYesNächster fest verabredeter Beginn am selben Tag.
nebenflaeche_geprueftYesPlatz und Wasseraufnahme an der Nebenfläche vor Ort bestätigt?

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 almost nothing: it does not say what the tool returns (no output schema exists), how the timing is combined (nass_ende + abtropf_min + umsetzen_min versus becken_faellig), or what happens when the drip area is not verified.

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 and front-loads the purpose, but the German sentence and the English gloss restate the same idea rather than adding complementary information, and the dash-joined structure reads as two fragments rather than a coherent spec.

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?

This is a five-parameter computation tool with no output schema, so the description should explain what result an agent gets back (boolean availability? slack minutes?) and how the inputs combine. It supplies neither, leaving the agent unable to interpret the outcome from the definition alone.

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 five parameters are documented in the schema itself, which sets the baseline at 3. The description only loosely gestures at the parameters ('bestätigte Nebenfläche' ↔ nebenflaeche_geprueft, 'abtropf' ↔ abtropf_min) without adding units, ranges, or interaction rules beyond what the schema provides.

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?

The description names a specific action (timing in a verified side/drip area for handing over an occupied sink) and ends with a plain-language check ('whether a verified drip area keeps the sink available for its next use'). However, the bilingual phrasing and abstract nouns ('Nutzungsuebergabe', 'Nebenfläche zeitlich einrechnen') make the actual computation hard to pin down, and it does not distinguish itself from close siblings such as pflege_spuelbecken_belegt_ausweichfolge.

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 to call this versus the other sink-related tools, no prerequisites (e.g. that the drip area must already be confirmed on site), and no exclusions. The word 'bestätigte' hints at a precondition but it is not framed as usage guidance.

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