Skip to main content
Glama

getecoback-raumklima

kompaktspuel_nicht_eingelegte_teile_auswahlgrund

Read-only

Trennt vorgeschriebene Ausnahmen, beobachtete Beladungsgrenzen und bisher ungeprüfte Stücke — Distinguish excluded items from observed fit issues and untested items.

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": {
      "noetig": "<noetig>",
      "eingelegt": "<eingelegt>",
      "material_ausgeschlossen": "<material_ausgeschlossen>",
      "praktisch_kein_platz": "<praktisch_kein_platz>"
    },
    "name": "kompaktspuel_nicht_eingelegte_teile_auswahlgrund"
  }
}

Input Schema

NameRequiredDescriptionDefault
noetigYesUnterschiedliche Stücke, die zum vollständigen Ergebnis gehören.
eingelegtYesDavon zulässig und normal eingelegt.
praktisch_kein_platzYesAndere nicht eingelegte Stücke mit bereits belegtem Platzproblem.
material_ausgeschlossenYesDavon durch genaue Unterlage als ungeeignet ausgegrenzt und nicht eingelegt.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is clear. The description adds the conceptual split between excluded, fit-limited, and untested items, but does not disclose validation rules, arithmetic consistency requirements, or what the tool returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact sentence with the key distinction front-loaded and no unnecessary wording. The bilingual repetition is concise and does not obscure the message.

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 four-required-parameter read-only classification tool, the description gives the main conceptual categories but omits how the counts relate to one another and what result the agent should expect. The detailed schema compensates substantially, but the definition remains minimal.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the parameters are already documented. The description adds useful conceptual meaning by distinguishing material exclusions from observed space limitations and by introducing “untested items,” a residual category not directly named in 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 states a specific verb, “Distinguish,” and names three categories: excluded items, observed fit issues, and untested items. This is clear enough to understand the classification purpose, though it does not explicitly differentiate this tool from similarly named dishwasher-related siblings.

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 description gives no explicit when-to-use guidance, prerequisites, or alternatives. It implies the tool is for categorizing non-loaded dishwasher items but does not say when this categorization should be selected over sibling tools.

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