Skip to main content
Glama

getecoback-raumklima

gebrauchtgeraet_video_ausschnitt_vollstaendiger_start

Read-only

Bei zwei Videosegmenten feststellen, ob der entscheidende Startmoment wirklich sichtbar ist — Detect gaps in recorded proof of a used-appliance start.

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": {
      "gleicher_lauf_belegt": "<gleicher_lauf_belegt>",
      "clip_a_start": "<clip_a_start>",
      "clip_a_end": "<clip_a_end>",
      "clip_b_start": "<clip_b_start>",
      "clip_b_end": "<clip_b_end>",
      "start_ab": "<start_ab>",
      "start_bis": "<start_bis>"
    },
    "name": "gebrauchtgeraet_video_ausschnitt_vollstaendiger_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
start_abYesErste Zeitmarke des zu belegenden kritischen Übergangs.
start_bisYesLetzte Zeitmarke dieses Übergangs.
clip_a_endYesLetzte sichtbare Zeitmarke A.
clip_b_endYesLetzte sichtbare Zeitmarke B.
clip_a_startYesErste Zeitmarke von Segment A.
clip_b_startYesErste Zeitmarke B.
gleicher_lauf_belegtYesSind beide Ausschnitte eindeutig demselben Lauf und derselben Zeitachse zugeordnet?

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 and the description's burden is lower. The description adds that the check concerns whether the decisive moment is 'really visible' across two segments, which is genuine analytical context. However, it does not disclose what the verdict looks like (no output schema exists), nor what happens when the clips are not from the same run — a case the schema itself flags via gleicher_lauf_belegt.

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 core statement is front-loaded and short. The bilingual structure is slightly wasteful — the English clause paraphrases the German rather than extending it — but both sentences remain short enough that nothing is genuinely padded.

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?

The tool takes seven required numeric/boolean parameters to reason about temporal coverage, and there is no output schema, so the description would ideally state the shape of the verdict (e.g. gap found / coverage satisfied) and how a false gleicher_lauf_belegt is handled. As written it explains the intent but not the result, which leaves a real gap for a computed-verdict tool.

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 seven parameters are already documented in German within the schema. The description adds only the framing that two segments (clip A and clip B) are compared around a critical transition, which loosely maps to the clip_* and start_* parameters without adding syntax or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 operation (feststellen / detect) and a specific resource (gaps in the recorded proof of a used-appliance start) across two video segments. An agent can tell this is a completeness/coverage check on video evidence rather than a general video tool. It does not explicitly set itself apart from the many sibling 'gebrauchtgeraet_*' evidence-checking tools, so it stops short of a 5.

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 use this versus alternatives, no prerequisites, and no exclusions. The agent must infer from the name and the sibling family that this is the gap-detection step after obtaining two clips. The phrase 'der entscheidende Startmoment' hints at the scenario but gives no actionable routing 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