Skip to main content
Glama

getecoback-raumklima

fensterbehang_sichtschutz_termin_zwischen_pflege

Read-only

Vorhangwäsche mit einem festen Sichtschutztermin und verfügbarem Ersatz abgleichen — Check if a laundry window leaves a scheduled privacy gap.

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": {
      "abnehmen": "<abnehmen>",
      "wieder_da": "<wieder_da>",
      "privat_ab": "<privat_ab>",
      "privat_bis": "<privat_bis>",
      "ersatz_ab": "<ersatz_ab>",
      "ersatz_bis": "<ersatz_bis>",
      "ersatz_geprueft": "<ersatz_geprueft>"
    },
    "name": "fensterbehang_sichtschutz_termin_zwischen_pflege"
  }
}

Input Schema

NameRequiredDescriptionDefault
abnehmenYesAbnehmen des regulären Vorhangs, Minuten seit Mitternacht.
ersatz_abYesAb wann ein passender Ersatz nutzbar ist.
privat_abYesBeginn des geplanten Sichtschutzbedarfs.
wieder_daYesBestätigte früheste Rückkehr am selben Tag.
ersatz_bisYesBis wann der Ersatz nutzbar ist.
privat_bisYesEnde des geplanten Sichtschutzbedarfs.
ersatz_geprueftYesSichtschutz und erlaubte Montage des Ersatzes vor Ort 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?

The readOnlyHint and openWorldHint annotations already establish that this is a safe, closed-world check. The description adds the key behavioral framing that it is a gap check, but it does not describe the return shape or what happens if ersatz_geprueft is false. For a read-only check with annotation coverage, this is adequate but not rich.

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?

The description is one front-loaded sentence with no wasted wording. The bilingual phrasing is slightly redundant but still efficient and clear.

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?

For a read-only check with seven required parameters and no output schema, the description covers the purpose but not the expected return value or edge-condition behavior. The schema already explains all parameters, and annotations cover safety, but the description could do more to close the output/behavior gap.

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 seven parameters already have inline explanations in the schema. The description does not add any parameter-specific meaning beyond what the schema provides, which is acceptable at baseline 3 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.

Purpose4/5

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

The description states a specific comparison and decision: align curtain laundry with a fixed privacy schedule and available replacement, checking whether the laundry window leaves a privacy gap. It gives a clear verb+resource outcome without naming sibling tools, so it is strong but lacks explicit differentiation from the many other pflege tools.

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?

The purpose implies when to use this tool (planning laundry against a privacy need with a replacement), but there are no explicit when/when-not conditions nor alternatives such as other scheduling tools. Usage is inferable rather than stated.

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