Skip to main content
Glama

getecoback-raumklima

klimafenster_reissverschluss_zwei_endpositionen

Read-only

Vergleicht am ruhenden Stoff die nutzbaren Reißverschlusspositionen mit zwei eigenen Auslasspositionen — Match recorded zipper travel to two outlet locations in the same seal.

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": {
      "min_position_mm": "<min_position_mm>",
      "max_position_mm": "<max_position_mm>",
      "auslass_a_mm": "<auslass_a_mm>",
      "auslass_b_mm": "<auslass_b_mm>"
    },
    "name": "klimafenster_reissverschluss_zwei_endpositionen"
  }
}

Input Schema

NameRequiredDescriptionDefault
auslass_a_mmYesGemessener Sollpunkt der ersten Anordnung ab derselben Marke in mm.
auslass_b_mmYesSollpunkt der zweiten Anordnung ab derselben Marke in mm.
max_position_mmYesDokumentiertes Ende ab derselben Marke in mm.
min_position_mmYesDokumentierter Anfang der nutzbaren Positionen ab Stoffmarke in mm.

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 two genuinely useful behavioral constraints beyond that: the fabric must be at rest, and all values are measured from the same reference mark ("dabsellben Marke" appears in the schema too). It says nothing about what the comparison yields, however.

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 verb and object first, plus a bilingual gloss. The duplication between the German and English halves carries marginal extra value but is compact and wastes no space.

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

Completeness4/5

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

For a four-parameter, read-only comparison with full schema coverage, the essential preconditions (static fabric, common datum) are present. The notable gap is that no output schema exists and the description never says what the comparison returns, leaving the agent to guess the result shape.

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 all four mm-valued parameters are already documented with minima/maxima. The description reinforces the pairing of auslass_a/auslass_b as the two outlet positions and the shared reference datum, but adds no units, tolerances, or interpretation rules beyond the schema.

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 verb ("Vergleicht" / "Match") and specific objects: the usable zipper positions against two outlet positions on the same seal. It is clear enough to distinguish from sibling operations like Zeitfolge or Materialbedarf tools, though it offers no explicit sibling naming or differentiation.

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 call this versus any alternative, no prerequisites, and no exclusions. The only implicit usage cue is "am ruhenden Stoff" (on the resting/static fabric), which suggests a measurement-time precondition but is not framed as guidance.

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