Skip to main content
Glama

getecoback-climate-weather

winterfenster_zugluft_pruefen

Read-only

Kalte Scheibe, undichte Fuge oder schlecht schließenden Fensterflügel unterscheiden — Distinguish window downdraught, seal leaks and closing problems.

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": {
      "sensation": "<sensation>",
      "closes_properly": "<closes_properly>",
      "seal_damaged": "<seal_damaged>"
    },
    "name": "winterfenster_zugluft_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
sensationYesWo wird Luftbewegung beobachtet?
seal_damagedYesIst die Dichtung sichtbar beschädigt oder fehlt sie?
closes_properlyYesSchließt und verriegelt der Flügel normal?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 and the description need not restate it. The description's own contribution is behavioral only in a weak sense — it discloses that the tool's job is to discriminate among three fault classes, but not what the result looks like (a classification, a ranked cause, a recommended fix) or how ambiguous inputs are resolved. With annotations carrying the safety burden, this is adequate but thin.

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 that names the symptom cases before anything else, with no filler or preamble. The German/English duplication is redundant for a German-language parameter set but serves as cheap disambiguation, so the cost is small.

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 simple read-only three-boolean/enum triage tool with full schema coverage and no output schema, the definition is close to sufficient, and annotations cover safety. What is left unstated is the shape of the outcome — whether the tool returns a single cause verdict, a list of candidate causes, or follow-up actions — which matters for a tool whose entire value is a classification.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds genuine mapping value: the three named fault classes correspond one-to-one with the three required inputs (cold pane → sensation=glass, leaking joint → seal_damaged, poor closing → closes_properly). That tells the agent how the diagnosis is driven by the inputs, not just what the inputs are called.

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 gives a specific diagnostic verb ('unterscheiden' / distinguish) plus the concrete fault classes it separates: cold pane draught, leaking seal joint, and a poorly closing window sash. An agent can infer the tool performs fault triage on a window from these three named cases. It stops short of naming a sibling diagnostic tool (e.g. fenster_oberflaeche_taucheck or fenster_beschlag_einordnen) that it should be preferred over, so it is clear but not sibling-differentiated.

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 only implied: the agent must infer that this applies when a draught or cold-window symptom is observed and the cause is unclear. There is no explicit 'use when' clause, no prerequisite (e.g. that the window is closed and locked during observation), and no statement of when another sibling tool would be the better choice.

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