Skip to main content
Glama

getecoback-climate-weather

duschbrause_schlauch_ruhezone_und_entnahmepfad

Read-only

Beobachtete Kreuzungen des vorhandenen Schlauchs beim Ablegen und beim Entnehmen getrennt dokumentieren — Separate route obstructions in two observed use states.

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": {
      "ruhelage": "<ruhelage>",
      "entnahme": "<entnahme>",
      "gleiche_route": "<gleiche_route>"
    },
    "name": "duschbrause_schlauch_ruhezone_und_entnahmepfad"
  }
}

Input Schema

NameRequiredDescriptionDefault
entnahmeYesBeobachteter Ort während des erlaubten normalen Entnehmens.
ruhelageYesBeobachteter Ort des vorhandenen Schlauchs ohne Nutzung.
gleiche_routeYesIst die markierte benutzte Spur in beiden Notizen gleich?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 safety and scope are covered structurally. The description adds the meaningful behavioral point that the two use states are recorded separately rather than merged. It does not say what is returned, whether a record is created/persisted, or how conflicting observations are handled.

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?

A single compact sentence with the core distinction front-loaded, followed by a brief English gloss. The bilingual restatement is somewhat redundant but short enough not to cost much. No filler or hedging.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only capture tool with three required enum parameters, full schema coverage, and no output schema, the description supplies everything needed to call it correctly: what to observe, in which two states, and that they must be kept separate. Nothing essential is missing.

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 three parameters are already documented in the schema, making 3 the baseline. The description does add a little meaning by emphasizing the separation of the two observation states, which clarifies why 'ruhelage' and 'entnahme' are distinct fields and what 'gleiche_route' is comparing.

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 verb ('dokumentieren' / 'Separate ... in two observed use states') and a concrete resource: observed crossings of the existing hose. It also states the key distinction — stowing ('Ablegen') versus removal ('Entnehmen') — so an agent understands it captures two separate observations rather than one. No sibling tool is named, so it stops short of full differentiation.

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 by 'Beobachtete Kreuzungen ... beim Ablegen und beim Entnehmen' — the agent can infer it applies when recording an observation of the hose in these two states. There is no explicit when-not guidance, no prerequisites, and no pointer to any alternative recording tool.

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