Skip to main content
Glama

getecoback-raumklima

laufrolle_abrollstrecke_pro_umlaeufe_sichtkontrolle

Read-only

Vergleicht eigene beobachtete Weglänge mit der kinematischen Referenz markierter Rollenumläufe — Compare observed travel to the no-slip reference for counted wheel turns.

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": {
      "umfang_mm": "<umfang_mm>",
      "umdrehungen": "<umdrehungen>",
      "weg_mm": "<weg_mm>",
      "gleicher_abschnitt": "<gleicher_abschnitt>"
    },
    "name": "laufrolle_abrollstrecke_pro_umlaeufe_sichtkontrolle"
  }
}

Input Schema

NameRequiredDescriptionDefault
weg_mmYesZugehörige beobachtete gerade Verlagerung in mm.
umfang_mmYesSeparat bekannter Rollenumfang in der beobachteten Konfiguration in mm.
umdrehungenYesGezählte volle und anteilige Umdrehungen.
gleicher_abschnittYesDerselbe sichtbare Durchgang, kein Wenden und derselbe Beginn und Schluss?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already establish read-only and closed-world behavior, while the description adds the conceptual no-slip reference model. It does not disclose tolerances, assumptions, or what the comparison result represents, so it adds only moderate context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single bilingual sentence front-loads the comparison action and has no filler. The German and English versions are tightly parallel, and every clause contributes to the stated purpose.

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 four-parameter read-only calculation with no output schema, the description explains the core comparison but omits the result format, tolerance behavior, and usage context. It is adequate to invoke but leaves gaps about interpreting the result and when the check applies.

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 the input schema already defines all four parameters, including units, bounds, and the meaning of gleicher_abschnitt. The description reinforces the observed-distance/reference-turns relationship but adds no parameter syntax or usage constraints 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 states a specific action: comparing an observed travel distance against a kinematic no-slip reference derived from counted wheel turns. It goes beyond restating the tool name, though it does not clarify what the visual-inspection result represents or distinguish it from any alternatives.

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 when-to-use or when-not-to-use guidance and no named alternative tool. The only usage cue is the implied comparison scenario, so an agent must infer the appropriate context from the purpose sentence alone.

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