Skip to main content
Glama

getecoback-raumklima

arbeitsplatz_technikumschaltung_eindeutige_proben

Read-only

Beim Wechsel von Bildschirm und Schreibtischlicht nur Abschnitte auswerten, in denen genau ein dokumentierter Zustand neu war — Recover single-change monitor or desk-light observations before comparing temperatures.

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": {
      "nachproben": "<nachproben>",
      "nur_bildschirm": "<nur_bildschirm>",
      "nur_licht": "<nur_licht>",
      "beide_wechsel": "<beide_wechsel>",
      "pc_last_gleich": "<pc_last_gleich>"
    },
    "name": "arbeitsplatz_technikumschaltung_eindeutige_proben"
  }
}

Input Schema

NameRequiredDescriptionDefault
nur_lichtYesWeitere Proben, in denen nur der Lichtzustand geändert war.
nachprobenYesZahl aller Nachproben mit protokollierten Umschaltungen.
beide_wechselYesWeitere Proben mit beiden Wechseln vor der Nachprobe.
nur_bildschirmYesDavon Proben, in denen nur der Bildschirmzustand geändert war.
pc_last_gleichYesPC-Last und Messposition blieben in den Einzelwechseln ausreichend vergleichbar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 safety is covered. The description adds the substantive behavioral rule that only single-change sections should be evaluated, but it does not disclose what the result looks like, whether counts are validated, or what happens when pc_last_gleich is false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loads the filtering condition, but it is a single bilingual sentence that partially repeats itself in German and English. The English 'Recover single-change monitor or desk-light observations' is not a clean restatement of 'nur Abschnitte auswerten', which adds ambiguity rather than clarity.

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?

This is a five-parameter tool with no output schema, so the description carries full responsibility for explaining what is returned. It never does: there is no indication whether the tool returns filtered samples, counts, a validation verdict, or how the numeric inputs are used. That is a substantial gap for an agent trying to invoke 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 all five parameters are already documented in the input schema. The description adds the conceptual notion of single-change sections, which loosely maps to nur_bildschirm, nur_licht, and beide_wechsel, but it does not explain how nachproben or pc_last_gleich affect behavior beyond what the schema says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific operation: evaluating only sections where exactly one documented state was new when switching monitor and desk light, and recovering single-change observations before comparing temperatures. However, it never states what the tool actually produces or how the five count/boolean parameters feed into that evaluation, so an agent can grasp the domain but not the exact action.

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 gives a clear usage condition ('Beim Wechsel von Bildschirm und Schreibtischlicht nur Abschnitte auswerten...') and a sequencing hint ('before comparing temperatures'). It does not name any sibling tool or state when not to use this one, leaving the agent to infer alternatives from the crowded arbeitsplatz_* family.

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