Skip to main content
Glama

getecoback-raumklima

kuechen_dosierloeffel_stueckbedarf_stufenplan

Read-only

Bei zwei tatsächlich verfügbaren, für denselben kalten Stoff geprüften Löffelgrößen eine geplante Mengenstufe ohne Teilfüllung treffen — Match one quantity using measured whole dry scoops of two sizes.

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": {
      "ziel_g": "<ziel_g>",
      "klein_g": "<klein_g>",
      "gross_g": "<gross_g>",
      "max_grosse_loeffel": "<max_grosse_loeffel>"
    },
    "name": "kuechen_dosierloeffel_stueckbedarf_stufenplan"
  }
}

Input Schema

NameRequiredDescriptionDefault
ziel_gYesVorgeplante Trockenmenge in Gramm.
gross_gYesGemessene Gramm eines gestrichenen großen Löffels.
klein_gYesGemessene Gramm eines gestrichenen kleinen Löffels.
max_grosse_loeffelYesWie viele große Löffel sollen im Vergleich höchstens eingesetzt werden?

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 annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful constraint that only whole scoops of two measured sizes are used and partial filling is excluded, but it does not disclose the return shape, whether an exact match is required, or what happens when no valid combination exists.

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?

It is a single front-loaded sentence with no filler beyond the bilingual duplication. The em-dash split is readable, though the German half is syntactically heavy.

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-parameter pure-calculation tool with full schema coverage and read-only annotations, the definition is adequate but incomplete. It does not say what the tool returns or how infeasible scoop combinations are handled, and there is no output schema to fill that gap.

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 four parameters are already documented in the input schema. The description does not add syntax, units, or edge-case meaning beyond restating the two spoon sizes and the target quantity.

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 specific calculation: matching a planned quantity using whole dry scoops of two measured spoon sizes, with no partial filling. The bilingual phrasing is a bit dense, but the English half makes the core operation clear enough to distinguish it from unrelated sibling tools.

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?

It gives an implicit when-to-use condition: two spoon sizes are actually available and tested for the same cold substance, and the user wants a planned quantity step without partial filling. It does not explicitly say when not to use it or name any alternative tool.

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