Skip to main content
Glama

getecoback-climate-weather

geraeterollen_schwenkbewegung_mitte_ausserhalb_endlagen

Read-only

Prüft ob der beobachtete Seitenüberstand während einer Richtungsänderung über beide Endstände hinausging — Compare observed midpoint sweep with both recorded endpoints.

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": {
      "vorher_mm": "<vorher_mm>",
      "zwischen_mm": "<zwischen_mm>",
      "nachher_mm": "<nachher_mm>",
      "punkt_gleich": "<punkt_gleich>"
    },
    "name": "geraeterollen_schwenkbewegung_mitte_ausserhalb_endlagen"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorher_mmYesÄußerste beobachtete Kante vor der Drehung ab fester Seitenmarke in mm.
nachher_mmYesEntsprechende Kante danach in mm.
zwischen_mmYesEntsprechende Kante in der beobachteten Zwischenlage in mm.
punkt_gleichYesGleiche Seitenmarke und belegter Aufbau während derselben regulären Bewegung?

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 verification criterion (comparing the observed midpoint sweep against both endpoints), but does not say what the tool returns (presumably a boolean verdict), what tolerance applies, or how a failed comparison is reported, leaving meaningful behavioral gaps.

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 short and front-loads the check. The English sentence largely duplicates the German sentence rather than adding new information, which is mild redundancy, but overall there is little wasted space.

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 validation tool, the schema fully documents inputs and annotations cover safety, but there is no output schema and the description never states the return value or result semantics. The reference to 'both recorded endpoints' is also unsupported by the parameter list, leaving a small interpretive gap an agent must resolve.

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 coverage is 100%, so all four parameters (vorher_mm, zwischen_mm, nachher_mm, punkt_gleich) are documented in the schema with meaningful descriptions and ranges. The tool description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the work.

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 check — whether the observed side overhang during a direction change exceeds both end positions — using a clear verb ('Prüft' / 'Compare') and a named resource (midpoint sweep vs. recorded endpoints). It does not differentiate this check from any sibling tool, and the phrase 'beide Endstände' is puzzling because no endpoint parameters exist, slightly muddying what is being compared.

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?

The definition gives no when-to-use or when-not-to-use guidance, no named alternative check, and no preconditions (e.g., that a direction change and stable mounting are required). The only usage signal is the boolean parameter 'punkt_gleich', which is not explained in the description.

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