Skip to main content
Glama

getecoback-raumklima

spuelgang_nachsortieren_besteckprobe

Read-only

Messen, wie viel Vorsortieren beim Besteck das spätere Umsortieren verändert. — Measure the effect of pre-sorting cutlery on secondary handling.

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": {
      "gleiche_anzahl_besteckteile": "<gleiche_anzahl_besteckteile>",
      "vorsortiergriffe_alt": "<vorsortiergriffe_alt>",
      "vorsortiergriffe_neu": "<vorsortiergriffe_neu>",
      "nachsortiergriffe_alt": "<nachsortiergriffe_alt>",
      "nachsortiergriffe_neu": "<nachsortiergriffe_neu>"
    },
    "name": "spuelgang_nachsortieren_besteckprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorsortiergriffe_altYesZusätzliche Sortiergriffe vor dem Lauf im bisherigen Ablauf.
vorsortiergriffe_neuYesZusätzliche Sortiergriffe vor dem Lauf im geänderten Ablauf.
nachsortiergriffe_altYesZusätzliche Sortiergriffe nach dem Lauf bisher.
nachsortiergriffe_neuYesZusätzliche Sortiergriffe nach dem Lauf im geänderten Ablauf.
gleiche_anzahl_besteckteileYesPro Ablauf gleich viele Besteckteile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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. The description adds that this is a comparative measurement between old and new procedures, but it does not state what kind of result is produced or whether the comparison is returned as a delta, ratio, or other structure.

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

Conciseness3/5

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

The description is short, but the German sentence and its English translation duplicate the same content rather than adding complementary detail. It is front-loaded and readable, but the bilingual repetition does not fully earn its 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?

For a five-parameter read-only calculation with full schema coverage and no output schema, the definition is minimally adequate. It explains the conceptual comparison but leaves the return value and usage context underspecified.

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 five parameters are already documented in the schema. The description adds no further meaning about the parameter units or how old and new values are paired, which is acceptable at baseline but not enriching.

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: measuring how much pre-sorting cutlery affects later re-sorting. It is clear what the tool computes, though it does not explicitly distinguish itself from sibling dishwashing-cycle analyses such as spuelgang_nachwaschaufwand.

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?

There is no explicit when-to-use guidance, no exclusions, and no mention of alternatives among the sibling tools. The context implies a dishwashing experiment comparison, but an agent is left to infer when this measurement is appropriate.

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