Skip to main content
Glama

getecoback-raumklima

pflege_benutztes_set_durchgang_zum_sammelplatz

Read-only

Benutzte Teile auf belegter direkter Route zur Sammelstelle bewegen, bevor der gemeinsame Zugang angefragt wird — Check whether a used-item return blocks a separate planned access window.

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": {
      "routenfreigabe": "<routenfreigabe>",
      "route_start": "<route_start>",
      "hinweg": "<hinweg>",
      "abgabe": "<abgabe>",
      "rueckweg": "<rueckweg>",
      "zugang_ab": "<zugang_ab>",
      "rueckweg_gleicher_engpass": "<rueckweg_gleicher_engpass>"
    },
    "name": "pflege_benutztes_set_durchgang_zum_sammelplatz"
  }
}

Input Schema

NameRequiredDescriptionDefault
abgabeYesBeobachtete Dauer der Abgabe.
hinwegYesBeobachtete Dauer bis dorthin.
rueckwegYesBeobachtete Dauer für die Rückkehr.
zugang_abYesZeit, zu der die andere Nutzung den Durchgang benötigt.
route_startYesAbmarsch zur Sammelstelle.
routenfreigabeYesSind Sammelstelle, Weg und getrennter Transport dieser benutzten Teile belegt?
rueckweg_gleicher_engpassYesWird derselbe nur einzeln nutzbare Durchgang auch bei der Rückkehr belegt?

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 safety profile is covered. The description adds the sequencing constraint (this must be settled before the shared access is requested) but says nothing about what verdict is produced or how a blocked route is reported; the "bewegen" wording sits in mild tension with readOnlyHint but describes the modelled scenario rather than a real write.

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?

Two compact sentences with no filler, and the scenario is stated up front. The two clauses partly restate each other in German and English, which is a small redundancy but not bloat.

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 seven-parameter, no-output-schema tool the description covers the scenario but not the result: it never says what the check returns or how a conflict is signalled, which is the main thing an agent needs beyond the well-documented inputs.

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% and every one of the seven required parameters carries a German explanation (durations in minutes, the routenfreigabe and rueckweg_gleicher_engpass booleans). The description adds no parameter-level meaning beyond that, 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 scenario: moving used parts along an occupied direct route to the collection point, and the English clause sharpens it to checking whether a used-item return blocks a separately planned access window. That is specific enough to separate it from the neighbouring pflege_* scheduling tools, though it wavers between an imperative ("bewegen") and a check, leaving slight doubt whether the tool plans or only validates.

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?

"bevor der gemeinsame Zugang angefragt wird" gives an ordering condition – run this before requesting the shared access window – which is real usage context. But it names no alternative tool and states no exclusion or precondition failure case, so when-not guidance has to be inferred.

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