Skip to main content
Glama

getecoback-raumklima

kuehlschrank_drei_vier_sterne_einfrieren_fachtyp

Read-only

Liest das belegte Sternfach für Lagerung und geplantes Einfrieren frischer Ware, besonders den Unterschied zwischen drei und vier Sternen — Interpret a documented freezer compartment type before buying

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": {
      "fachtyp": "<fachtyp>",
      "bedarf_frische_ware": "<bedarf_frische_ware>"
    },
    "name": "kuehlschrank_drei_vier_sterne_einfrieren_fachtyp"
  }
}

Input Schema

NameRequiredDescriptionDefault
fachtypYesFachtyp aus Produktdatenblatt des exakten Modells.
bedarf_frische_wareYesDer Haushalt muss zusätzlich frische Ware einfrieren und nicht nur Tiefkühlware lagern.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

With readOnlyHint=true and openWorldHint=false already declared, the safety profile is covered; the description adds that the input is documentation-based (a product datasheet) and that the interpretation turns on storage versus freezing fresh goods. It does not state what form the interpretation takes or whether it returns a suitability verdict, which is the main behavioral gap for a lookup tool.

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 definition is short and front-loads the German statement, but it is bilingual with substantial overlap between the two halves, and the English clause mostly repeats the German one while appending only "before buying" as new information. The space is not wasted outright, but trimming would lose nothing.

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 two-parameter, fully documented, closed-world lookup this is close to sufficient, and no output schema exists so return values need not be explained. Still, an agent cannot tell from the description whether the result is a yes/no suitability answer or explanatory text, which matters before invoking it for a buying decision.

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 coverage is 100%, so both parameters and the enum values are already fully documented in the schema. The description reinforces the meaning of the fresh-goods boolean (storage vs planned freezing) and the 3/4-star distinction, but adds no syntax or edge-case guidance (e.g. how "offen" is treated). Baseline 3 is appropriate.

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?

"Interpret a documented freezer compartment type" states a concrete verb and resource, and the German clause narrows the scope to the three-star vs four-star distinction for storage versus planned freezing of fresh food. The purpose is discernible without opening the schema, though the German verb "Liest" (reads) slightly obscures that this is an interpretation of datasheet data rather than a physical read.

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?

"Before buying" frames the usage as a pre-purchase decision check, which is useful implied context, and the emphasis on the 3-vs-4-star difference signals when this tool matters. However, no alternative tool is named and no exclusion criteria are given, so the agent must infer that sibling tools like the Kellerfach target-temperature datasheet lookup are for other compartments.

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