Skip to main content
Glama

getecoback-raumklima

roboter_hindernis_umweg_bedienzeit

Read-only

Beobachtete Rückfahrten am Durchgang von der eigentlichen Bedienzeit trennen. — Separate observed passage detours from hands-on intervention.

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": {
      "messfahrten": "<messfahrten>",
      "rueckfahrten_dabei": "<rueckfahrten_dabei>",
      "bedieneingriffe": "<bedieneingriffe>",
      "eingriffsminuten": "<eingriffsminuten>"
    },
    "name": "roboter_hindernis_umweg_bedienzeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
messfahrtenYesGleiche Fahrten durch denselben Durchgang.
bedieneingriffeYesFahrten, bei denen eine Person eingreifen musste.
eingriffsminutenYesGemessene aktive Eingriffsminuten insgesamt.
rueckfahrten_dabeiYesZusätzliche Rückfahrten oder Wendemanöver am Durchgang.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 that the tool computes a separation between detours and intervention time, but does not explain assumptions, output format, or how the four inputs are combined.

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 definition is two short sentences and front-loads the operation. The English sentence duplicates the German translation, but the overall wording is efficient and free of filler.

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?

For a calculation tool with four required inputs and no output schema, the description omits what result will be returned, the output units, and how the inputs map to the separation. An agent cannot determine what value to expect or how to interpret it.

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%, with each numeric parameter individually documented, such as 'Fahrten, bei denen eine Person eingreifen musste.' The description adds no additional meaning, formula, or interpretation beyond what the schema already provides, fitting the baseline for high schema coverage.

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 verb and resource: separating observed return trips at the passage from actual hands-on operating time. It is clearly a calculation tool, though it does not name sibling alternatives or explicitly distinguish itself from similar robot tools.

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 when-to-use guidance, no prerequisites, and no alternatives mentioned. The sentence only restates the operation; an agent must infer the context from the tool name and parameter set.

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