Skip to main content
Glama

getecoback-raumklima

spuelmaschine_vorbereitung_aufgaben_besetzung

Read-only

Zwei feste Küchenaufgaben auf zwei Personen nach bestätigter Zuständigkeit verteilen — Check whether two concurrent dishwasher prep roles can be staffed.

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": {
      "a_kann_sortieren": "<a_kann_sortieren>",
      "a_kann_einraeumen": "<a_kann_einraeumen>",
      "b_kann_sortieren": "<b_kann_sortieren>",
      "b_kann_einraeumen": "<b_kann_einraeumen>",
      "parallel_machbar": "<parallel_machbar>"
    },
    "name": "spuelmaschine_vorbereitung_aufgaben_besetzung"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kann_sortierenYesPerson A kann zum vereinbarten Zeitpunkt sortieren.
b_kann_sortierenYesPerson B kann zum vereinbarten Zeitpunkt sortieren.
parallel_machbarYesGetrennte Arbeitsplätze und die vorgesehene Beladung wurden abgestimmt.
a_kann_einraeumenYesPerson A kann zum selben Zeitpunkt am Gerät einräumen.
b_kann_einraeumenYesPerson B kann zum selben Zeitpunkt am Gerät einräumen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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. The description adds the 'confirmed responsibility' condition but does not explain what the boolean inputs are evaluated against, whether the tool merely reports feasibility, or what result shape the caller should expect.

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 description is short and front-loaded with the staffing scope. The German-first, English-second phrasing is slightly redundant, but nothing is superfluous.

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?

For a read-only check with five required booleans and no output schema, the description is minimally adequate: it states the feasibility question but omits the return value and how the five boolean conditions combine. The schema covers parameter meanings, but the missing output expectation is a real 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 the baseline is 3. The description refers to two people and two concurrent roles, which loosely maps to the five booleans, but it adds no parameter-level meaning 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 names a specific operation — checking whether two concurrent dishwasher prep roles can be staffed — and mentions the two-person/two-task staffing scope. It is distinguishable from sibling dishwasher tools, though the German verb 'verteilen' slightly muddies whether the tool assigns or only checks.

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?

It gives a precondition ('nach bestätigter Zuständigkeit') but no explicit guidance on when to use this tool versus alternatives, nor when not to use it. The agent must infer its role from the description alone.

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