Skip to main content
Glama

getecoback-raumklima

monitor_sichtprobe_raumlicht_und_bildinhalt

Read-only

Vor einem Helligkeitsvergleich Monitorproben mit geändertem Bildinhalt und geändertem Tageslicht getrennt aussondern — Audit screen appearance observations for content and room-light confounders.

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": {
      "paare": "<paare>",
      "gleicher_inhalt": "<gleicher_inhalt>",
      "gleiches_raumlicht": "<gleiches_raumlicht>",
      "modus_ueberprueft": "<modus_ueberprueft>"
    },
    "name": "monitor_sichtprobe_raumlicht_und_bildinhalt"
  }
}

Input Schema

NameRequiredDescriptionDefault
paareYesAnzahl ursprünglich gepaarter Beobachtungen desselben Monitors.
gleicher_inhaltYesDavon Paare mit unverändertem Referenzbild.
modus_ueberprueftYesDavon wiederum Paare mit nachvollziehbar gleichem vorgesehenem Monitormodus.
gleiches_raumlichtYesDavon wiederum Paare mit ausreichend gleichem Umgebungslicht und gleicher Beobachtungsposition.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the tool is known to be a safe read. The description adds that it separates content and room-light confounders, but it never discloses that the four counts must be nested subsets (each ≤ its parent) or what it returns when they are inconsistent.

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?

Two tight sentences (German plus an English restatement) with the key constraint front-loaded. No padding, though the em-dash dual-language restatement is slightly redundant.

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?

There is no output schema and the tool is read-only, so the description carries little burden. Still, for a four-parameter audit of nested counts, it should say more about the required hierarchy among paare, gleicher_inhalt, modus_ueberprueft and gleiches_raumlicht to call it correctly.

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 schema already documents all four count parameters. The description only echoes two of them (Bildinhalt, Tageslicht) and adds nothing about 'modus_ueberprueft' or the required ordering of the counts, so it does not exceed the baseline.

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 action (auditing/filtering monitor appearance observations) and two concrete confounders it targets: changed image content and changed daylight. This distinguishes it from generic inspection siblings, but the dense German phrasing ('getrennt aussondern') keeps it from being fully self-evident.

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?

It implies a timing cue — use this before performing a brightness comparison — but gives no explicit exclusions, no sibling routing, and no statement about what to do if the audit fails.

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