Skip to main content
Glama

getecoback-climate-weather

kuehlgeraet_gitter_pflegeschritt

Read-only

Sichtbar verstaubtes Lüftungsgitter ohne Geräteeingriff als Pflegepunkt priorisieren — Choose a manual-approved or support step for dusty fridge vents.

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": {
      "staub_sichtbar": "<staub_sichtbar>",
      "zugaenglich": "<zugaenglich>",
      "pflege_erlaubt": "<pflege_erlaubt>"
    },
    "name": "kuehlgeraet_gitter_pflegeschritt"
  }
}

Input Schema

NameRequiredDescriptionDefault
zugaenglichYesDie Öffnung ist ohne Ausbau oder Öffnen einer Gehäuseabdeckung zugänglich?
pflege_erlaubtYesDie Methode für genau dieses Gitter ist in der Modellanleitung beschrieben?
staub_sichtbarYesStaub ist außen an der vorgesehenen Lüftungsöffnung sichtbar?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the meaningful constraint that the appliance must not be opened or disassembled and that the method must be manual-approved. Beyond that it discloses nothing about the decision logic or the returned recommendation, which is the core value of a triage tool.

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?

Two short sentences with the decisive condition (visible dust, no device intervention) front-loaded. The only waste is that the German and English halves restate the same content rather than one complementing the other.

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?

With three fully documented required booleans and no output schema, the description has little structural support to lean on for results: it never says what the tool returns (a ranked care step? a support referral? a boolean release?). It is adequate to trigger the call but not to predict its outcome.

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 three booleans (dust visible, accessible without removing a cover, method described in the model manual) are already documented. The description echoes two of these conditions in prose but adds no format, ordering, or edge-case semantics beyond the schema, so the baseline of 3 applies.

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 resource (a visibly dusty ventilation grille on a cooling appliance) and a specific action (prioritize/choose a maintenance or support step). It is clear enough that an agent knows this is a triage/decision tool rather than a measurement or repair tool, though it never states what the chosen step is returned as.

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 is implied by the preconditions in the text ('sichtbar verstaubtes', 'ohne Geräteeingriff'), so an agent can infer this applies only to externally visible dust with no disassembly. No explicit when-not condition or named alternative sibling is given, and escalation behavior ('support step') is mentioned but not scoped.

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