Skip to main content
Glama

getecoback-raumklima

gefrierfach_leerbehaelter_rueckstellprobe

Read-only

Mit leeren Behältern prüfen, welche beim Zurückstellen im Gefrierfach einen zweiten Griff brauchen. — Use empty containers to check freezer-drawer restowing friction.

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": {
      "rueckstellversuche": "<rueckstellversuche>",
      "direkt_passend": "<direkt_passend>",
      "nach_drehung_passend": "<nach_drehung_passend>"
    },
    "name": "gefrierfach_leerbehaelter_rueckstellprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
direkt_passendYesDavon ohne Umorientieren zurückgestellte Behälter.
rueckstellversucheYesAlle vorgesehenen Rückstellversuche mit leeren Alltagsbehältern.
nach_drehung_passendYesDavon mit erst nach Drehen oder Verschieben erreichtem vorgesehenem Platz.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The read-only and non-open-world annotations already cover the safety profile. The description adds the concrete test method, empty containers and second-grip criterion, but does not explain how inputs are processed or what result to 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 definition is compact and front-loads the test method. The bilingual duplication is slightly 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.

Completeness3/5

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

For a read-only three-parameter probe with no output schema, the description is adequate but incomplete. It does not explain what the three counts produce or how an agent should interpret the result.

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 schema fully defines the three numeric counts. The description adds no extra meaning about how those parameters relate to the test outcome.

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 gives a specific verb and resource: checking with empty containers which items need a second grip when restowed in the freezer. It is clear what the tool does, but it does not distinguish itself from any sibling tool.

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?

The description implies the use case, testing freezer restowing friction with empty containers, but gives no explicit when-not guidance and names no alternatives.

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