Skip to main content
Glama

getecoback-climate-weather

fensterplatte_markierungen_nach_abnahme

Read-only

Wieder eingesetzte Fensterplatte an zwei eigenen Markierungen mit der Ausgangslage abgleichen — Compare a removable panel reinstallation with two marked reference points.

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": {
      "start_links_cm": "<start_links_cm>",
      "neu_links_cm": "<neu_links_cm>",
      "start_rechts_cm": "<start_rechts_cm>",
      "neu_rechts_cm": "<neu_rechts_cm>",
      "toleranz_cm": "<toleranz_cm>"
    },
    "name": "fensterplatte_markierungen_nach_abnahme"
  }
}

Input Schema

NameRequiredDescriptionDefault
toleranz_cmYesEigene Mess- und Markiertoleranz je Punkt.
neu_links_cmYesJetzt gemessene Position an der linken Markierung.
neu_rechts_cmYesJetzt gemessene Position an der rechten Markierung.
start_links_cmYesUrsprünglich markierte Position links entlang derselben Rahmenkante.
start_rechts_cmYesUrsprünglich markierte Position rechts auf derselben Skala.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety is covered. The description adds no behavior beyond that: it never says what the comparison yields (per-side deviation? a pass/fail verdict against toleranz_cm?), whether out-of-tolerance input errors out, or in what units/structure results come back. For a tool with no output schema, this is a real gap.

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 with the action first and the English restatement second; nothing is padding. The bilingual duplication costs a little space but improves matching for an inconsistently named tool.

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?

With five required numeric parameters, no output schema, and no annotations explaining semantics, the description should say what result an agent gets and what tolerance does. It says neither, so an agent cannot tell how to interpret the response or whether a tolerance breach is reported or raised.

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 every parameter is already documented in the input schema, including the start/neu left/right pairing and the tolerance. The description only reinforces that the two marks are 'eigene' (self-set) and the reference is the 'Ausgangslage', which maps to what the schema already states. Baseline 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 gives a concrete verb and resource: it aligns a re-inserted window panel against its original position using two self-set marks. That is far clearer than the opaque German tool name alone. It does not differentiate itself from any sibling (e.g. schubladen_markierungen_zuordnen, which sounds adjacent), so it stops short of a 5.

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 by the phrase 'Wieder eingesetzte Fensterplatte' — i.e. call this after re-installing a removable panel. There is no explicit when-not condition, no mention of prerequisites (that the original marks must still exist), and no named alternative for other measurement checks.

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