Skip to main content
Glama

getecoback-raumklima

wohnmobil_polster_rueckkehr_fachzugang_termin

Read-only

Trenne den Zeitpunkt, an dem ein Fach wieder zugänglich ist, vom möglichen Termin zum Rückstellen ausgelagerter Polster — Compare camper storage access with the later return of furnishings

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": {
      "fach_sichtpruefung_tag": "<fach_sichtpruefung_tag>",
      "polster_bereit_tag": "<polster_bereit_tag>",
      "nutzung_tag": "<nutzung_tag>",
      "beide_zeiten_bestaetigt": "<beide_zeiten_bestaetigt>"
    },
    "name": "wohnmobil_polster_rueckkehr_fachzugang_termin"
  }
}

Input Schema

NameRequiredDescriptionDefault
nutzung_tagYesTag, bis zu dem der Platz für seine gewöhnliche Aufgabe wieder benötigt wird
polster_bereit_tagYesBestätigter Tag, an dem die ausgelagerten Polster wieder bereitliegen
fach_sichtpruefung_tagYesTag des bestätigten freien Zugangs und der Sichtprüfung der ursprünglichen Einbaustelle
beide_zeiten_bestaetigtYesKeiner der Termine ist lediglich vorgesehen

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, and the description is consistent with a read-only comparison rather than a mutation. However, it does not disclose what the comparison returns, whether the confirmed-dates flag gates evaluation, or any other behavioral constraints.

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 a compact, front-loaded sentence with no wasteful preamble. The German and English versions duplicate the same idea, which is slightly redundant but still 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 four-required-parameter read-only comparison, the description explains the core distinction between access and return dates. It omits the meaning of the comparison result and the role of the required confirmation flag, and with no output schema the definition does not fully explain what an agent receives back.

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 are already documented in the schema. The description adds a conceptual mapping between access timing and furnishings return, but says nothing specific about nutzung_tag or beide_zeiten_bestaetigt beyond what the schema provides.

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 between when a compartment is accessible and when stored cushions are returned; the verb 'Trenne/Compare' and the resource are clear. It does not explicitly distinguish this tool from similarly named sibling tools, so it falls short of a 5.

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?

Usage is implied: use this when you need to separate the compartment-access date from the later furnishings-return date. There is no explicit when-not guidance or routing to alternatives, so the guidance remains adequate but incomplete.

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