Skip to main content
Glama

getecoback-raumklima

gaesteraum_morgenlicht_fruehe_nutzung

Read-only

Schlafenden Gast und morgendlichen Lichtbedarf bei nur einem Sichtschutz zeitlich abstimmen — Coordinate a guest’s dark window with the room’s next morning use.

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": {
      "dunkel_bis": "<dunkel_bis>",
      "licht_ab": "<licht_ab>",
      "rueckbau_min": "<rueckbau_min>",
      "leise_alternative_bestaetigt": "<leise_alternative_bestaetigt>"
    },
    "name": "gaesteraum_morgenlicht_fruehe_nutzung"
  }
}

Input Schema

NameRequiredDescriptionDefault
licht_abYesFrühester gewünschter Beginn der Tageslicht-Nutzung.
dunkel_bisYesAbgesprochenes Ende der Verdunkelung am Morgen.
rueckbau_minYesVor Ort beobachtete Zeit zum geräuscharmen Abnehmen und Verstauen.
leise_alternative_bestaetigtYesIst eine separat beleuchtete Ausweichfläche für den Morgen tatsächlich nutzbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 by structured data. The description adds the operative constraint ('bei nur einem Sichtschutz' — only one privacy screen), which is real context, but says nothing about what is compared, whether conflicts are reported or resolved, or how the four required inputs are weighed. There is also mild tension between 'zeitlich abstimmen' (arrange/coordinate) and the read-only annotation, though it does not rise to a contradiction.

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 the constraint is front-loaded, but the English sentence is a near-verbatim translation of the German one and contributes almost no new information. Half the text is duplication rather than added specification.

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 four-required-parameter tool with no output schema, the description gives no indication of the return value or decision logic — e.g. whether it returns a boolean feasibility result, the binding constraint, or a recommended shift. Given the scenario-evaluation nature and the absence of any output schema, this is a meaningful gap an agent cannot fill from structured fields.

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 four parameters (dunkel_bis, licht_ab, rueckbau_min, leise_alternative_bestaetigt) are already documented in the schema. The description adds no format, unit, or interpretation detail beyond what the properties state. Baseline 3 applies 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.

Purpose3/5

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

The description names the two things being reconciled (a guest's dark window and the room's next morning light use) and the constraint of a single privacy screen, so the domain is identifiable. However, the verb 'abstimmen/coordinate' leaves unclear what the tool actually produces — a feasibility verdict, a computed schedule, or a stored arrangement. The obscure tool name provides no help, and no sibling tool is referenced to disambiguate.

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 this tool should be chosen, no preconditions, and no alternatives despite many sibling scenario tools covering adjacent scheduling/room-use questions. The agent must infer from the German title alone that this is the guest-room morning-light conflict case.

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