Skip to main content
Glama

getecoback-raumklima

spuelprogramm_fertig_bis

Read-only

Prüfen, ob das Geschirr mit einem passenden Spülprogramm bis zur gewünschten Nutzung fertig ist — Check whether a suitable programme fits a dish-ready deadline.

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": {
      "verfuegbare_min": "<verfuegbare_min>",
      "start_in_min": "<start_in_min>",
      "programm_min": "<programm_min>",
      "ausraeumen_min": "<ausraeumen_min>"
    },
    "name": "spuelprogramm_fertig_bis"
  }
}

Input Schema

NameRequiredDescriptionDefault
programm_minYesDokumentierte oder beobachtete Dauer des passenden Programms.
start_in_minYesGeplanter Start in Minuten ab jetzt.
ausraeumen_minYesEigener Puffer zum Entnehmen oder Ausräumen.
verfuegbare_minYesZeit von jetzt bis zum gewünschten Zeitpunkt in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 the safety profile is covered and the description correctly reads as a pure evaluation. Beyond that it adds little: it does not say what form the verdict takes (boolean, slack minutes, suggested latest start) even though there is no output schema to supply that.

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?

A single well-formed sentence with the checking verb front-loaded, followed by an English paraphrase that duplicates rather than extends the German. The bilingual restatement is mildly redundant but does not obscure the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, fully documented, read-only arithmetic check with no output schema, the definition covers the essential contract: what is compared against what. The only real omission is the shape of the answer (feasible plus margin versus a bare boolean), which is a modest 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%, so all four parameters are already documented in the schema, establishing a baseline of 3. The description only loosely gestures at the inputs ('passendes Spülprogramm' for programm_min, 'bis zur gewünschten Nutzung' for verfuegbare_min) and says nothing about start_in_min or ausraeumen_min.

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 (Prüfen / Check) applied to a specific resource (Geschirr mit passendem Spülprogramm) bounded by a deadline (bis zur gewünschten Nutzung). An agent can tell this is a feasibility computation, not an action on a device. It does not differentiate itself from any sibling, which is the only thing keeping it from a 5.

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: the agent must infer that this is called when planning whether a rinse cycle will finish before the dishes are needed. No when-not conditions, no prerequisites (e.g. that a programme must already be chosen), and no named alternatives are given.

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