Skip to main content
Glama

getecoback-raumklima

gebrauchtgeraet_laufzeiten_verschiedene_zeitgrenzen

Read-only

Zwei angebliche Programmdauern nur aus vergleichbaren Start- und Endmarken neu bilden — Normalize seller-reported duration for omitted startup and finish segments.

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": {
      "beide_abschnitte_belegt": "<beide_abschnitte_belegt>",
      "a_kern_min": "<a_kern_min>",
      "a_ausgelassen_min": "<a_ausgelassen_min>",
      "b_kern_min": "<b_kern_min>",
      "b_ausgelassen_min": "<b_ausgelassen_min>"
    },
    "name": "gebrauchtgeraet_laufzeiten_verschiedene_zeitgrenzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kern_minYesSeparat aufgezeichneter Kernlauf A.
b_kern_minYesSeparat aufgezeichneter Kernlauf B.
a_ausgelassen_minYesBelegte notwendige Minuten außerhalb dieser Aufzeichnung A.
b_ausgelassen_minYesBelegte notwendige Minuten außerhalb dieser Aufzeichnung B.
beide_abschnitte_belegtYesSind Aufgaben, Anfangs- und Endmarken sowie fehlende Abschnitte beider Läufe wirklich vergleichbar?

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 annotations already establish that this is a read-only, non-open-world operation. The description adds useful context that it normalizes durations around omitted startup and finish segments, but it does not explain what happens when comparability is false or what the returned normalized values look like.

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 reconstruction operation. The German-English mix is slightly awkward, but the sentence is otherwise efficient and contains little wasted wording.

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 five-parameter computational tool with no output schema, the description explains the normalization concept but not the return shape or invalid-input behavior. It is adequate given rich schema coverage, but there are clear gaps around outputs and failure cases.

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 five parameters are already documented in the schema. The description reinforces that the operation depends on comparable start and end markers, but it does not add format or validation meaning beyond what the schema provides.

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 operation: reconstruct two alleged program durations from comparable start and end markers, and normalize seller-reported durations for omitted startup and finish segments. It is clear enough to distinguish the core task, but it does not explicitly contrast this tool with the many sibling used-device tools.

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 by the phrase 'nur aus vergleichbaren Start- und Endmarken' and by the seller-reported omitted segments scenario. However, there is no explicit when-to-use guidance, no when-not-to-use condition, and no named alternative tool.

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