Skip to main content
Glama

getecoback-climate-weather

gefriergeraet_eisschicht_verlauf

Read-only

Rasche Rückkehr einer Eisschicht als beobachteten Verlauf für den Service erfassen — Record repeat frost at the same location without diagnosing a defect.

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": {
      "tage_seit_pflege": "<tage_seit_pflege>",
      "beobachtungen": "<beobachtungen>",
      "erneut_gesehen": "<erneut_gesehen>",
      "verfahrensgleich": "<verfahrensgleich>"
    },
    "name": "gefriergeraet_eisschicht_verlauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
beobachtungenYesAnzahl vergleichbarer Sichtkontrollen an derselben Stelle.
erneut_gesehenYesKontrollen mit erneut sichtbarer Eisschicht.
tage_seit_pflegeYesVergangene Tage seit dem nach Anleitung abgeschlossenen Pflegevorgang.
verfahrensgleichYesVergleichbare Stelle und unverändertes Beobachtungsverfahren?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior1/5

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

The description's central verb is 'erfassen' (record/capture) an observed history for the service, which describes a data-entry action, while the annotations declare readOnlyHint=true. No other behavior (persistence, side effects, what the service record affects) is disclosed to reconcile the two, so the safety profile an agent would infer from the text conflicts with the annotation.

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?

It is a single front-loaded sentence, which is good, but the German clause and the English clause restate the same content, so a meaningful share of the text does not add new information.

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?

All four required parameters are schema-documented and no output schema exists, so the structured data carries most of the burden. However, for a tool described as capturing a record, the description never clarifies what the observation is stored against or whether anything is persisted, leaving the write/read question unresolved.

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 required parameters (beobachtungen, erneut_gesehen, tage_seit_pflege, verfahrensgleich) are already explained in the schema. The description adds no additional meaning about their units, comparability constraints, or how the ratio of observations to repeat sightings is interpreted.

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 action and subject: capture a rapidly returning ice layer as an observed history for service records, at the same location, without diagnosing a defect. It distinguishes itself from diagnostic siblings by explicitly excluding fault diagnosis. The bilingual restatement is redundant but the core purpose is unambiguous.

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?

Usage context is implied (a repeat frost observation at the same location following a completed care procedure), and one exclusion is stated ('ohne Defektdiagnose'). No sibling or alternative tool is named, so the agent must infer when this is preferable to a diagnostic or maintenance 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