Skip to main content
Glama

getecoback-climate-weather

gefrierschrank_no_frost_fachscope_nachweis

Read-only

Trenne die ausgewiesene automatische Entfrostung des Vier-Sterne-Fachs von beobachteten Feuchtespuren — Separate declared auto-defrost scope from observed frost or moisture

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": {
      "genaues_modell": "<genaues_modell>",
      "fundort": "<fundort>",
      "geraetewert_zugeschrieben": "<geraetewert_zugeschrieben>"
    },
    "name": "gefrierschrank_no_frost_fachscope_nachweis"
  }
}

Input Schema

NameRequiredDescriptionDefault
fundortYesOrt der tatsächlichen Beobachtung
genaues_modellYesGenaue deutsche Modellkennung der geprüften Variante
geraetewert_zugeschriebenYesDie Beobachtung wurde demselben Gerät und der aktiven Nutzung zugeordnet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/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 structurally. The description adds the conceptual framing that inputs are observations to be kept separate from manufacturer declarations, which is meaningful context beyond the annotations. It does not say whether anything is persisted, what the result looks like, or what happens when fundort is 'unklar'.

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?

A single front-loaded sentence stating the separation task, followed by a bilingual restatement. The German-first phrasing puts the operative content first, and the English gloss aids non-German readers; the duplication is the only minor cost.

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 3-parameter read-only tool with no output schema, the description covers the domain intent but not the result: an agent cannot tell what a successful call returns or how a 'Nachweis' is represented. Combined with the absence of usage routing among many similar siblings, the definition is workable but leaves real gaps.

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% and every parameter carries its own description plus two enums, so the schema does the documentation work. The description reinforces the split between declared scope and observed evidence, which loosely motivates geraetewert_zugeschrieben, but adds no syntax, format, or edge-case detail beyond the schema. 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 names a domain-specific operation — separating the declared auto-defrost behaviour of the four-star compartment from observed frost/moisture traces — which is enough to recognise the subject area. However, it never says what the tool mechanically does: whether it produces a 'Nachweis' record, an evaluation verdict, or a comparison result. The sibling list is dominated by similarly named *_nachweis tools, and nothing here distinguishes this one from, say, abtauereignis_energie_lueckenfreie_zuordnung.

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 explicit when-to-use or when-not-to-use guidance and no alternative is named. The declared-vs-observed framing implies a situation (a documented defrost claim needs to be reconciled with an actual observation) but the agent must infer it. No prerequisites, no mention of what input conditions make this the right tool over the numerous sibling evidence tools.

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