Skip to main content
Glama

getecoback-climate-weather

spueler_servicetiefe_geraet_und_arbeitsbereich

Read-only

Einen vom Service benannten Arbeitsraum für die Geräteentnahme getrennt von der freien Küchennutzung festhalten — Keep temporary service extraction clearance distinct from an ordinary aisle.

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": {
      "frei_mm": "<frei_mm>",
      "service_mm": "<service_mm>",
      "arbeitsplatz_getrennt": "<arbeitsplatz_getrennt>",
      "arbeitsplatz_gesehen": "<arbeitsplatz_gesehen>",
      "service_bezug_belegt": "<service_bezug_belegt>"
    },
    "name": "spueler_servicetiefe_geraet_und_arbeitsbereich"
  }
}

Input Schema

NameRequiredDescriptionDefault
frei_mmYesGemessene freie Tiefe vor dem Gerät entlang der bestätigten Serviceachse.
service_mmYesVom zuständigen Service für den Termin mitgeteilte freie Tiefe auf derselben Achse.
arbeitsplatz_gesehenYesDie getrennte Fläche ist tatsächlich zugänglich und vor Ort bestätigt?
service_bezug_belegtYesMessbezug und benötigte Tiefe für genau dieses Gerät und diesen Termin geklärt?
arbeitsplatz_getrenntYesEin weiterer Arbeitsbereich wurde vom Service als separat benötigt 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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description reinforces the domain scoping but does not explain what the tool returns, how the measurements and booleans are evaluated, or any permission or output behavior. It does not contradict the annotations.

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 that states the purpose and the key distinction without extraneous detail. The German/English restatement is somewhat repetitive but serves a bilingual clarification role.

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 tool with five required parameters and no output schema, the description establishes the domain purpose but leaves open what the tool returns and how the measurements and confirmation booleans combine. It is adequate when paired with the rich schema, but not fully self-contained.

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 parameter has a detailed field description. The tool description adds no additional parameter-level meaning, 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 states a specific verb, "festhalten" (record), and a specific resource, a service-designated work area for device extraction kept distinct from ordinary kitchen use. It does not explicitly differentiate this tool from any sibling tool, 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?

The phrase "getrennt von der freien Küchennutzung" / "distinct from an ordinary aisle" implies the usage context: documenting temporary service extraction clearance rather than ordinary circulation. However, it gives no explicit when-to-use condition, exclusions, or alternative tool routing.

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