Skip to main content
Glama

getecoback-raumklima

fensterbeschlag_fotopaar_innen_aussen_abgleich

Read-only

Prüfe, welcher Scheibenseite eine zeitlich passende Beschlagbeobachtung zugeordnet werden kann — Attribute matched condensation evidence to the observed glass surface

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": {
      "foto_seite": "<foto_seite>",
      "gegenprobe_seite": "<gegenprobe_seite>",
      "gegenprobe_beschlagen": "<gegenprobe_beschlagen>",
      "zeitabstand_min": "<zeitabstand_min>",
      "toleranz_min": "<toleranz_min>"
    },
    "name": "fensterbeschlag_fotopaar_innen_aussen_abgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
foto_seiteYesScheibenseite, die das erste Foto nachweisbar zeigt
toleranz_minYesGrößter für diese Beobachtung noch akzeptierter Zeitabstand
zeitabstand_minYesAbstand der beiden Beobachtungen in Minuten
gegenprobe_seiteYesScheibenseite der zweiten protokollierten Sichtbeobachtung
gegenprobe_beschlagenYesAuf der zweiten protokollierten Seite war Beschlag sichtbar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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. Beyond that the description adds essentially nothing: it does not state the decision outcome (what a positive vs. negative assignment looks like), whether toleranz_min is inclusive, or how the 'offen' enum value is treated. The one behavioural hint — that the match is temporal — is already encoded in the zeitabstand_min/toleranz_min parameters.

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?

Short, with the operation front-loaded, but the em-dash English half is a pure paraphrase of the German half and earns nothing. Two clauses of the same content make the definition look bilingual rather than informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A read-only decision tool with five mandatory, fully documented parameters and no output schema needs the description to explain the verdict semantics and the tolerance edge cases. That is exactly what is missing, leaving the agent unable to predict what it will get back from a call.

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% and both enums are documented with per-value meanings, so the schema carries the parameter burden. The description adds no syntax, units, or interaction rules (e.g. how zeitabstand_min relates to toleranz_min). Baseline 3 applies when the schema does the heavy lifting.

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 first clause names a check verb and the objects involved (glass side vs. a temporally fitting condensation observation), so the general idea is graspable. But it never says what the tool actually returns — an assignment decision, a boolean match, or a ranked candidate — and it does not distinguish itself from the many other *_abgleich siblings. The trailing English fragment merely restates the German rather than sharpening the purpose.

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 when-to-use guidance, no exclusion, and no named alternative among the sibling tools. An agent must infer from the parameter names alone that this is for reconciling two photo observations of a pane. Nothing says what to do when the observations fall outside the tolerance or when the sides conflict.

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