Skip to main content
Glama

getecoback-climate-weather

kuehlschrank_entnahme_umraeumgriffe

Read-only

Messen, wie viele andere Behälter beim Zugriff auf häufig genutzte Behälter bewegt werden. — Compare moves of other containers when retrieving frequently used ones.

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_entnahmen": "<gleiche_entnahmen>",
      "umraeumgriffe_alt": "<umraeumgriffe_alt>",
      "umraeumgriffe_neu": "<umraeumgriffe_neu>",
      "neue_umraeumfaelle": "<neue_umraeumfaelle>"
    },
    "name": "kuehlschrank_entnahme_umraeumgriffe"
  }
}

Input Schema

NameRequiredDescriptionDefault
gleiche_entnahmenYesGleiche Probeentnahmen mit jedem der beiden Fachaufbauten.
umraeumgriffe_altYesAndere Behälter vorher bewegt, einschließlich Rückstellen.
umraeumgriffe_neuYesAndere Behälter nach der Änderung bewegt, einschließlich Rückstellen.
neue_umraeumfaelleYesProbeentnahmen, bei denen im neuen Aufbau erstmals ein anderer Behälter bewegt werden musste.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

readOnlyHint=true and openWorldHint=false already tell the agent this is a closed-world pure read/compute operation, so the description's only marginal value is naming the metric. It does not disclose what is returned (a difference, a ratio, a per-case count) despite there being no output schema, leaving the result shape opaque.

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 German sentence is compact and front-loaded, but the English half restates it verbatim rather than adding information, so roughly half the text is duplication rather than earned content.

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?

With four required numeric parameters, no output schema, and a computation distinguishing an old from a new setup, the definition should at minimum say what quantity is produced and how the inputs combine. It covers only the general idea of counting moved containers, which is not enough to call it correctly or interpret the result.

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 four numeric fields (gleiche_entnahmen, umraeumfriffe_alt/neu, neue_umraeumfaelle) are already documented in the input schema. The description adds no constraint, unit, or relationship between the old and new counts, so the baseline 3 applies.

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 gives a verb ('Messen'/'Compare') and a resource ('andere Behälter ... beim Zugriff'), but it is not clear that this is an arithmetic comparison between an old and a new fridge configuration built from four count inputs. An agent reading only this line cannot tell whether the tool observes a physical process or computes a delta from the supplied numbers.

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 statement of when to use this versus closely named siblings such as kuehlschrank_einraeumfolge or kuehlschrank_griffseite_routinenvergleich, nor any prerequisite, exclusion, or input-condition guidance. The sentence is purely descriptive of the metric.

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