Skip to main content
Glama

getecoback-climate-weather

pflege_notiz_vor_reset_quittierung_ohne_verlust

Read-only

Vor einem dokumentierten Bedienungsreset prüfen, ob nur bestätigte abgeschlossene Aufgaben ausgeblendet werden — Preserve unresolved upkeep notes before a reset or dismissal.

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": {
      "reset_belegt": "<reset_belegt>",
      "bearbeitet_bestaetigt": "<bearbeitet_bestaetigt>",
      "weitere_anzeigen": "<weitere_anzeigen>",
      "davon_ausserhalb_notiert": "<davon_ausserhalb_notiert>"
    },
    "name": "pflege_notiz_vor_reset_quittierung_ohne_verlust"
  }
}

Input Schema

NameRequiredDescriptionDefault
reset_belegtYesSind Anlass und Reset-Wirkung für genau diese Anzeige dokumentiert?
weitere_anzeigenYesZusätzliche Meldungen, die laut Dokumentation mit verschwinden würden.
bearbeitet_bestaetigtYesIst der zum Reset gehörende tatsächliche Pflegeschritt quittiert?
davon_ausserhalb_notiertYesDavon separat mit bisherigem Bearbeitungsstand festgehalten.

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?

The readOnlyHint and openWorldHint annotations already establish that this is a safe, non-open-world read operation. The description adds useful context about the pre-reset check and the preservation concern, but the English wording 'Preserve unresolved upkeep notes' is slightly ambiguous about whether the tool merely validates or actively preserves notes; it does not clarify return behavior.

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 short and front-loads the reset context. The bilingual restatement in German and English is mildly redundant, but it remains compact and readable.

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 read-only validation tool with four fully documented required parameters, the invocation conditions are adequately covered. However, with no output schema, the description does not explain what the check returns or how an agent should interpret the result.

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 required parameters are already documented in the schema. The description adds the overall pre-reset loss-check context but no additional parameter-level meaning 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 names a specific check performed before a documented operating reset and identifies the resource/condition: whether only confirmed completed tasks would be hidden and unresolved upkeep notes preserved. It is understandable but does not explicitly distinguish itself from any similarly reset-related sibling tool, and the mixed German/English phrasing adds slight ambiguity.

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

Usage Guidelines4/5

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

It gives a clear usage context: before a documented reset or dismissal, and specifically when checking whether unresolved upkeep notes could be lost. It does not name when-not-to-use cases or alternative tools, but the context for invocation is explicit.

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