Skip to main content
Glama

getecoback-climate-weather

geraet_geteilt_verbrauch_bis_rueckgabe

Read-only

Gemeinsam genutztes Gerät samt Verbrauchsteilen zu späteren Übergaben planen — Track what a borrower should return with a shared household device.

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": {
      "teile_passend": "<teile_passend>",
      "uebergeben": "<uebergeben>",
      "vereinbarte_einsaetze": "<vereinbarte_einsaetze>",
      "je_wechsel": "<je_wechsel>",
      "eigentuemer_reserve": "<eigentuemer_reserve>",
      "mitgebrachtes_material": "<mitgebrachtes_material>"
    },
    "name": "geraet_geteilt_verbrauch_bis_rueckgabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
je_wechselYesTeile je vollständigem geplanten Wechsel.
uebergebenYesBei der ersten Übergabe vorhandene nutzbare Verbrauchsteile.
teile_passendYesSind die exakten Teile und die Mengen der vereinbarten Übergaben bestätigt?
eigentuemer_reserveYesBei der Rückgabe vereinbarter Sollbestand.
vereinbarte_einsaetzeYesVor der Rückgabe geplante Einsätze mit Wechsel.
mitgebrachtes_materialYesZusätzliche bestätigte nutzbare Teile, die bereitgelegt werden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/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's "planen" is consistent with a pure computation, so there is no contradiction. Beyond that consistency, the description discloses nothing behavioral: not that all inputs are required, not the unit semantics (parts per full cycle, opening stock, owner reserve), and no hint about what the computed result represents.

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 short sentences: a German purpose statement followed by an English one-liner, front-loaded with the domain object. There is no filler, though the bilingual duplication is mildly redundant rather than harmful.

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

Completeness2/5

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

With six required parameters and no output schema, the description should carry the burden of explaining what the tool returns — a plan, a per-cycle count, or a shortfall verdict — and it does not. Combined with the absent when-to-use guidance, an agent cannot predict the response shape from the definition alone.

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% — all six parameters carry German descriptions (e.g. je_wechsel as "Teile je vollständigem geplanten Wechsel", teile_passend as a confirmation flag). The description adds no additional meaning, so the baseline of 3 applies when the schema does the full explanatory work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a resource ("Gemeinsam genutztes Gerät samt Verbrauchsteilen") and the English gloss narrows the intent to "track what a borrower should return." However, the verb phrase "zu späteren Übergaben planen" is abstract, and nothing distinguishes this planning tool from similarly-named device/return siblings, so an agent still has to infer the concrete operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool, when not to, or which sibling to prefer, despite a crowded sibling space (e.g. geraet_zubehoer_beim_wechsel_getrennt_verplanen, ventilator_teilraum_hin_und_rueckgabe, textil_tauschbestand_bis_trocknung). The only usage cue is implicit in the phrase "zu späteren Übergaben."

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