Skip to main content
Glama

getecoback-raumklima

kuechenvorbereitung_schneidbrett_ablagen_verlust

Read-only

Beim selben Vorbereitungsvorgang volle, überfüllte und unbenutzte Sammelschalen aus einer Sichtprobe zählen — Identify capacity lost to incompatible prep bowls.

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": {
      "schalen": "<schalen>",
      "normal_benutzt": "<normal_benutzt>",
      "umgefuellt_weil_voll": "<umgefuellt_weil_voll>",
      "grund_fuer_umfuellen_bestaetigt": "<grund_fuer_umfuellen_bestaetigt>"
    },
    "name": "kuechenvorbereitung_schneidbrett_ablagen_verlust"
  }
}

Input Schema

NameRequiredDescriptionDefault
schalenYesBereitgestellte, gleichartige und für den kalten Versuch vorgesehene Schalen.
normal_benutztYesSchalen, die ohne zusätzliches Umfüllen benutzt werden konnten.
umgefuellt_weil_vollYesAndere Schalen, deren Inhalt wegen der erwarteten Füllgrenze separat umgefüllt wurde.
grund_fuer_umfuellen_bestaetigtYesBei jeder dafür gezählten Schale wurde die Füllgrenze als konkreter Anlass protokolliert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the figures derive from a single visual observation rather than measured instrumentation, which is genuinely useful context. It reveals nothing about what the tool returns (a count, a percentage, a loss figure) or how the boolean confirmation gate affects behavior.

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 text is short with no filler, but it is split awkwardly across two languages and the actual point — capacity lost — is deferred to the trailing English fragment instead of being front-loaded. The German clause and the English clause partially restate the same measurement rather than complementing each other efficiently.

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

Completeness4/5

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

Given four fully described required numeric/boolean parameters and no output schema, the description supplies the essential framing: it is a read-only counting exercise over one prep run yielding a loss estimate. What is missing is any hint of the arithmetic relationship between the counts (e.g., whether the overfilled and normally used bowls must sum against the supplied total) and what form the loss result takes.

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; each of the four parameters is already documented in the schema with ranges and meaning. The description's phrase 'volle, überfüllte und unbenutzte Sammelschalen' loosely maps onto the schalen / umgefuellt_weil_voll / normal_benutzt triple but adds no new semantics, and it never explains the role of grund_fuer_umfuellen_bestaetigt as a gating condition.

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 concrete action (counting full, overfull and unused Sammelschalen from a single visual sample) and states the derived goal in English: identifying capacity lost to incompatible prep bowls. An agent can tell this is a loss/capacity computation, not a lookup or a write. It stops short of distinguishing itself from any sibling, so it does not reach 5.

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 only usage constraint is the scoping phrase 'Beim selben Vorbereitungsvorgang', which requires all counted bowls to come from one prep run. There is no when-to-use vs. when-not-to-use guidance, no mention of prerequisites, and no routing to an alternative sibling tool for related capacity or bowl measurements.

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