Skip to main content
Glama

getecoback-climate-weather

fensterplatte_schliessprobe_abnahme_wiederholung

Read-only

Erfasst wiederkehrende Einschränkungen am Fenster nach Entnahme derselben Platte — Evaluate repeated changes in normal closure after removing the same plate.

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": {
      "versuche": "<versuche>",
      "auffaellig": "<auffaellig>",
      "baseline_belegt": "<baseline_belegt>"
    },
    "name": "fensterplatte_schliessprobe_abnahme_wiederholung"
  }
}

Input Schema

NameRequiredDescriptionDefault
versucheYesNormal beobachtete Schließvorgänge nach vollständiger Entnahme.
auffaelligYesDavon mit sichtbarer Abweichung von der regulären Stellung.
baseline_belegtYesWar die reguläre Schließstellung vor dem ersten Einsatz dokumentiert?

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. The description adds the context of repeated normal-closure changes after plate removal, but does not explain thresholds, how results should be interpreted, or any other behavior beyond the annotations. There is no contradiction with the read-only annotation.

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?

The description is a single compact bilingual sentence with the operation and conditioning scenario front-loaded. The English gloss repeats the German but aids comprehension, and there is no structural clutter or unnecessary detail.

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 read-only tool with three required parameters and full schema coverage, the description provides adequate domain framing. However, because there is no output schema, the description does not indicate what is returned or how the evaluation result should be interpreted, leaving a meaningful gap for an evaluation tool.

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?

All three parameters have full schema descriptions, so the schema carries the parameter semantics. The description does not add meaning beyond the schema—for example, it does not clarify what counts as 'auffällig' or how 'versuche' relates to the repeated evaluation. A baseline 3 is appropriate given 100% schema coverage.

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 operation—capturing or evaluating recurring closure limitations after the same plate is removed—and gives an English gloss. It is domain-specific and understandable, though the German 'Erfasst' and English 'Evaluate' are not perfectly aligned and no sibling tool is named.

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 explicit guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The clause 'nach Entnahme derselben Platte' provides scenario context but does not tell an agent when this tool is the right 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