Skip to main content
Glama

getecoback-raumklima

nachtlueften_schliessdienst_fristabdeckung

Read-only

Eine vorher abgestimmte Fensterübergabe prüfen, wenn die öffnende Person vor dem Schließtermin weg ist — Confirm that an accepting person can close the window within the agreed range.

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": {
      "offen_ab_min": "<offen_ab_min>",
      "schliessen_frueh_min": "<schliessen_frueh_min>",
      "schliessen_spaet_min": "<schliessen_spaet_min>",
      "person_b_frei_ab_min": "<person_b_frei_ab_min>",
      "person_b_hats_bestaetigt": "<person_b_hats_bestaetigt>"
    },
    "name": "nachtlueften_schliessdienst_fristabdeckung"
  }
}

Input Schema

NameRequiredDescriptionDefault
offen_ab_minYesGeplante Öffnung auf einer gemeinsamen Minutenachse ab Start des Zeitplans.
person_b_frei_ab_minYesPerson B kann ab dieser Minute übernehmen.
schliessen_frueh_minYesFrüheste vereinbarte Schließminute auf derselben Achse.
schliessen_spaet_minYesSpäteste vereinbarte Schließminute auf derselben Achse.
person_b_hats_bestaetigtYesB hat Aufgabe und die Erreichbarkeit der Bedienung bestätigt.

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 agent knows this is a safe, side-effect-free check. The description adds the framing that this is a confirmation of a pre-agreed arrangement, but it never states the nature of the result (a pass/fail verdict, a gap in minutes, or a reason on failure), which is the key behavior for a check tool.

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 trigger condition, which is good. However, the German sentence and the English sentence restate the same content rather than complementing each other, adding length without new information, and no sentence explains the outcome the check produces.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All five parameters are required and fully documented, so input is unambiguous. The main gap is the missing output contract: with no output schema and no statement of the verdict, an agent cannot tell whether a failed check is signaled by a boolean, an error, or a gap value — minor but worth noting.

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 coverage is 100% and all five required parameters carry descriptive German text explaining the shared minute axis, the agreed closing window, and person B's availability and confirmation. The description adds no meaning beyond the schema, so the baseline of 3 applies.

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 (prüfen/confirm) tied to a concrete scenario: verifying that an accepting person can close the window within the agreed range when the opener leaves before the closing deadline. The resource is somewhat abstract ('Fensterübergabe'), and no sibling tool is referenced, but the scenario is specific enough that an agent can distinguish this from unrelated household/ventilation checks.

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 one clear trigger condition: use it when the opening person is gone before the closing deadline and a pre-agreed handoff exists. It does not name an alternative tool or state when not to use it, and it does not clarify what to do if the handoff was not pre-agreed, so guidance remains implied rather than explicit.

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