Skip to main content
Glama

getecoback-raumklima

saugwischer_raumfreigabe_nach_beobachtung

Read-only

Nach eigener Beobachtung zwei bearbeitete Bodenabschnitte zum nächsten Zugang einplanen — Compare observed dry-back windows against a planned room reopening.

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": {
      "vergleichbarer_aufbau": "<vergleichbarer_aufbau>",
      "ende_a_min": "<ende_a_min>",
      "beobachtet_a_min": "<beobachtet_a_min>",
      "ende_b_min": "<ende_b_min>",
      "beobachtet_b_min": "<beobachtet_b_min>",
      "zugang_min": "<zugang_min>",
      "puffer_min": "<puffer_min>"
    },
    "name": "saugwischer_raumfreigabe_nach_beobachtung"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_a_minYesGeplantes Arbeitsende A, Minuten seit Mitternacht.
ende_b_minYesGeplantes Arbeitsende B, Minuten seit Mitternacht.
puffer_minYesSelbst gewählter Zusatzpuffer je Abschnitt.
zugang_minYesNächster benötigter gemeinsamer Zugang am selben Tag.
beobachtet_a_minYesBeobachtete Zeit bis zum gewünschten Zustand A nach dessen Arbeitsende.
beobachtet_b_minYesBeobachtete Zeit bis zum gewünschten Zustand B nach dessen Arbeitsende.
vergleichbarer_aufbauYesSind dokumentierte Bodenfreigabe, Einstellungen und Bedingungen mit den Beobachtungen vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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. The description adds that the calculation rests on the caller's own observations rather than stored data, which is useful context, but it says nothing about what the comparison produces or how ties/late access are handled.

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?

A single front-loaded sentence with no padding, and the bilingual phrasing keeps the core action clear. The duplicated German/English wording is slightly redundant but costs little.

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?

With seven required parameters and no output schema, the description should explain what comes back (a feasibility verdict, a recommended access time, per-section slack). It does not, leaving the result shape entirely unspecified for a non-trivial computation.

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 every parameter (ende_a/b, beobachtet_a/b, zugang, puffer, vergleichbarer_aufbau) is already documented in the schema. The description only alludes to 'zwei bearbeitete Bodenabschnitte' as the A/B pairing and adds no syntax or interpretation beyond the schema.

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 concrete operation: comparing observed dry-back windows for two floor sections against a planned room reopening, and planning them for the next access. That is a specific verb-plus-resource statement an agent can match to a task, though it does not explicitly distinguish itself from siblings like saugwischer_bodenfreigabe.

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 explicit when-to-use guidance, no stated prerequisites, and no named alternative for cases where only one section or no observation exists. The agent must infer the scenario entirely from the phrase 'nach eigener Beobachtung'.

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