Skip to main content
Glama

getecoback-raumklima

pflege_tischfreigabe_zwei_genutzte_seiten

Read-only

Bei geteilter Arbeitsfläche geprüft freie und noch beanspruchte Seiten vor Rückkehr der nächsten Person abgleichen — Confirm whether a person needs one side or the entire shared surface.

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": {
      "von_beiden_kontrolliert": "<von_beiden_kontrolliert>",
      "a": "<a>",
      "b": "<b>",
      "naechster_bedarf": "<naechster_bedarf>"
    },
    "name": "pflege_tischfreigabe_zwei_genutzte_seiten"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesStatus der ersten Seite.
bYesStatus der zweiten Seite.
naechster_bedarfYesPlatzbedarf der nächsten Aufgabe.
von_beiden_kontrolliertYesSind beide Seiten auf aktuellen Zustand und verbindliche Belegung geprüft?

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 annotation already establishes that this is a safe read/check operation, and the description reinforces that it is a comparison/confirmation step. It does not explain what the result looks like or any side constraints, but with annotations carrying the safety profile this is adequate.

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 definition is a single front-loaded sentence with no filler. The bilingual German/English phrasing is somewhat redundant, but it does not bloat the description.

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 four-parameter, read-only check with full schema coverage, the description gives the operating context and intent. Since there is no output schema, it could have stated what the confirmation result is, but the missing detail is not severe.

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 and enum meanings are already documented in the schema. The description adds only the general scenario of comparing free and claimed sides, not additional syntax or conditional meaning for specific parameters.

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 action (abgleichen/confirm) on a specific resource (free and still-claimed sides of a shared work surface) before the next person returns. It is clear enough to distinguish the operation, though it does not explicitly contrast itself with the many sibling 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 timing condition 'vor Rückkehr der nächsten Person' gives implied usage context, and the shared-surface scenario narrows when the tool applies. However, it does not say when to avoid this tool or which sibling to use for adjacent checks.

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