Skip to main content
Glama

getecoback-raumklima

kuehlfach_auffindprobe_verwechslungszahl

Read-only

Zwei Anordnungen nach tatsächlich verwechselten und weiterhin nicht gefundenen Verpackungen vergleichen. — Compare mix-ups and misses in a refrigerator retrieval task.

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": {
      "suchaufgaben": "<suchaufgaben>",
      "verwechselt_alt": "<verwechselt_alt>",
      "verwechselt_neu": "<verwechselt_neu>",
      "nicht_gefunden_alt": "<nicht_gefunden_alt>",
      "nicht_gefunden_neu": "<nicht_gefunden_neu>"
    },
    "name": "kuehlfach_auffindprobe_verwechslungszahl"
  }
}

Input Schema

NameRequiredDescriptionDefault
suchaufgabenYesAnzahl identischer Suchaufgaben je Anordnung.
verwechselt_altYesAufgaben mit zuerst falsch ausgewählter Verpackung vor der Änderung.
verwechselt_neuYesAufgaben mit zuerst falsch ausgewählter Verpackung nach der Änderung.
nicht_gefunden_altYesAndere Aufgaben, in denen ohne Auswahl abgebrochen wurde, vor der Änderung.
nicht_gefunden_neuYesAndere Aufgaben, in denen ohne Auswahl abgebrochen wurde, nach der Änderung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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 the safety profile is covered. The description adds no behavioral context beyond that: it does not say how the counts are combined, whether counts must be consistent with suchaufgaben, or what the response contains.

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?

Two short sentences, front-loaded with the verb and object, with no filler. The German/English duplication is slightly redundant but serves a reasonable audience-broadening purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

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

This is a five-parameter computation tool with no output schema, so the description bears full responsibility for explaining what is returned. It says nothing about the result, making it hard for an agent to know what to do with the output or how to report it.

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 numeric parameters are fully documented in the schema itself. The description adds no meaning beyond that, but with complete schema coverage the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (vergleichen/compare) and a specific object (two arrangements on confused vs. not-found packages in a refrigerator retrieval task), which is more than a restatement of the name. However, it never explains what the comparison produces (a ratio, a corrected confusion count, a verdict), so the tool's actual output remains opaque.

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 guidance on when this tool should be chosen over the many sibling analysis tools, no prerequisites, and no exclusions. The agent must infer from the name alone that this is a before/after comparison of two arrangements.

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