Skip to main content
Glama

getecoback-raumklima

fenster_beschlag_einordnen

Read-only

Beschlag außen, innen oder zwischen Glasscheiben einordnen — Interpret the side on which window condensation is observed.

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": {
      "side": "<side>"
    },
    "name": "fenster_beschlag_einordnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYesSeite anhand einer erreichbaren Oberfläche prüfen: outside, inside, between, unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 does not contradict it. It adds nothing beyond that: no mention of how ambiguous or 'unknown' cases are resolved, no note that the result is purely an interpretive label rather than a measurement. With annotations carrying safety, 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?

Two short clauses, front-loaded with the German action and followed by the English gloss. Nothing is wasted, though the bilingual duplication means the second half largely repeats the first rather than adding 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?

For a one-parameter read-only classifier with no output schema, the description is minimally sufficient: an agent knows what label to produce. It is incomplete in that it never says what the classification is used for downstream or how to handle the 'unknown' fallback, which is the one decision an agent might get wrong.

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 the single parameter is an enum with all four values documented, including the practical test ('Seite anhand einer erreichbaren Oberfläche prüfen'). The description adds no further meaning about how to choose between inside/between/unknown, so it sits at the baseline the schema sets.

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 German clause names a specific verb (einordnen/classify) and resource (Beschlag on a window: outside, inside, or between panes). The English gloss restates the same action, so the intent is graspable, but it does not differentiate this tool from sibling window diagnostics such as fenster_oberflaeche_taucheck or fensterabdichtung_laenge.

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 statement of when to use this classification versus other window tools, no precondition that condensation must have been observed, and no exclusion of cases. The only hint is the parenthetical about interpreting the observed side, which implies context rather than stating it.

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