Skip to main content
Glama

getecoback-raumklima

spuelmaschine_deckel_belegen_tellerplaetze

Read-only

Prüfen, wie viele Tellerplätze nach einer zulässigen Deckelbeladung gemeinsam nutzbar bleiben. — Account for plate positions displaced by compatible lids.

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": {
      "tellerplaetze_ohne_deckel": "<tellerplaetze_ohne_deckel>",
      "deckel_geplant": "<deckel_geplant>",
      "tellerplaetze_je_deckel": "<tellerplaetze_je_deckel>",
      "teller_geplant": "<teller_geplant>"
    },
    "name": "spuelmaschine_deckel_belegen_tellerplaetze"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckel_geplantYesZulässig eingeplante gleichartige Deckel.
teller_geplantYesTeller, die gleichzeitig mit den Deckeln in die Ladung sollen.
tellerplaetze_je_deckelYesDurch jeden Deckel zusätzlich belegte Tellerplätze bei gleicher Anordnung.
tellerplaetze_ohne_deckelYesTatsächlich nutzbare Tellerplätze ohne Deckel.

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 annotations already establish that this is a read-only, closed-world check, and the description is consistent with that by framing it as "Prüfen". It adds useful domain context about compatible lids and displaced positions, but does not disclose the computation logic, edge cases, or whether the result can be negative.

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 short and front-loaded with the core check. The English gloss largely restates the German sentence, which is slightly redundant, but it does not obscure the purpose or waste much space.

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 four required numeric parameters and no output schema, the description should clarify the return value more explicitly. It implies a count of remaining usable plate positions, but omits edge behavior and the relationship between inputs and output, leaving some gaps for a calculation tool.

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 the four numeric parameters are fully documented in the schema itself. The description reinforces the domain relationship between lids and plate positions but adds no syntax, constraints, or interpretation beyond the parameter names and schema descriptions.

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 check ("Prüfen, wie viele Tellerplätze ... nutzbar bleiben") and a clear domain resource (plate positions after permissible lid loading). It does not explicitly differentiate this calculation from the many sibling dishwasher tools, so it falls short of 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "nach einer zulässigen Deckelbeladung" implies the scenario, but there is no explicit when-to-use guidance, no exclusions, and no named alternative among the many sibling tools. An agent must infer the planning context entirely.

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