Skip to main content
Glama

getecoback-climate-weather

vorhang_pflege_nachmessung_aufhaengung

Read-only

Gepflegte Vorhangbahn anhand eines selbst festgelegten Bodenabstands neu einhängen — Map a measured curtain drop to a feasible hanging adjustment.

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": {
      "aufhaenger_verstellbar": "<aufhaenger_verstellbar>",
      "hoehe_cm": "<hoehe_cm>",
      "behange_laenge_cm": "<behange_laenge_cm>",
      "zielabstand_cm": "<zielabstand_cm>",
      "hochstell_cm": "<hochstell_cm>",
      "tiefstell_cm": "<tiefstell_cm>"
    },
    "name": "vorhang_pflege_nachmessung_aufhaengung"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoehe_cmYesUnterkante des bisherigen Aufhängepunkts über dem Boden.
hochstell_cmYesNach oben verfügbarer Verstellweg.
tiefstell_cmYesNach unten verfügbarer Verstellweg.
zielabstand_cmYesGewählter Bodenabstand.
behange_laenge_cmYesTrockene Falllänge nach der Pflege.
aufhaenger_verstellbarYesIst Verstellen bei dieser Befestigung zulässig und nachvollziehbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint and openWorldHint annotations already establish this as a safe, closed-world computation, so the description only needs to add context. It contributes the notion of feasibility but never states what the tool returns (a recommended position? a yes/no verdict?) or how it behaves when the target clearance is unreachable — a real gap for a 6-parameter calculator with no output schema.

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 sentences, front-loaded with the concrete scenario and followed by an English gloss for agents that do not parse German. The bilingual duplication costs a little space but earns it by disambiguating a compound German tool name.

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?

All six required parameters are documented in the schema and the read-only nature is covered by annotations, so the essentials are present. What is missing is the decision surface: whether an infeasible combination is rejected or clamped, and what the result looks like, neither of which any structured field supplies.

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 every parameter carries a precise German definition, so the schema does the heavy lifting. The description adds no per-parameter meaning — notably it does not explain the direction convention (hoehe_cm measured to the underside of the current hanging point) or how hochstell_cm/tiefstell_cm bound the feasible result.

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 sentence plus English gloss both state a specific verb and resource: re-hanging a maintained curtain panel based on a self-chosen floor clearance, framed as mapping a measured drop to a feasible adjustment. This is clear enough to pick out from the curtain-adjacent siblings (Packungsbreite, Parkbreite), though no sibling is named as a contrast.

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 implied rather than stated: the tool applies after care when a measured drop must be reconciled with a desired floor clearance, and 'feasible' hints that the adjustability of the hanger matters. There is no explicit when-not guidance, no mention of what to do when the requested clearance exceeds the available travel, and no named alternative.

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