Skip to main content
Glama

getecoback-raumklima

roboter_stillstand_letzte_dokumentierte_ladung

Read-only

Prüfe eine längere dokumentierte Nichtnutzung gegen die Aufbewahrungsvorgabe und markiere eine fehlende letzte Ladung — Check complete months since a documented storage charge

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": {
      "modell": "<modell>",
      "laengere_lagerung": "<laengere_lagerung>",
      "letzte_ladung_bestaetigt": "<letzte_ladung_bestaetigt>",
      "volle_monate_seit_ladung": "<volle_monate_seit_ladung>"
    },
    "name": "roboter_stillstand_letzte_dokumentierte_ladung"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständiger Modellname am Gerät für die deutsche Ausführung
laengere_lagerungYesEs geht um eine aufbewahrte und länger nicht benutzte Einheit
letzte_ladung_bestaetigtYesLetzte dokumentierte Ladung mit eindeutigem Kalendertag am genau zugeordneten Roboter
volle_monate_seit_ladungYesVolle Kalendermonate seit dieser Ladung; bei fehlendem Datum nur Platzhalter

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, so the description need only add context beyond that. Instead it repeats the check framing and uses 'markiere', which is ambiguous for a read-only tool and could mislead an agent into expecting a mutation rather than a read-only flag in the response. Nothing is said about what the check returns or what happens when the date is missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The check condition is front-loaded and the sentence is short, but the content is duplicated verbatim in German and English without the English half adding precision. Half the text is redundancy rather than new information.

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?

With four required parameters and no output schema, the description should at least convey what the check produces and how the retention threshold is applied. It conveys the check's subject but not its result shape or the handling of the placeholder-month edge case, leaving a moderate gap for a read-only evaluation tool.

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% with per-parameter descriptions and an enum, so the schema carries parameter meaning. The description only gestures at 'volle Monate seit Ladung' and adds no interpretation of the model enum, the placeholder case for a missing date, or the interaction between laengere_lagerung and letzte_ladung_bestaetigt.

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 states a check operation ('Prüfe ... gegen die Aufbewahrungsvorgabe') on a specific quantity ('volle Monate seit einer dokumentierten Ladung'), so the core purpose is inferable. However, 'markiere eine fehlende letzte Ladung' is vague about what marking means in a read-only tool, and the description never distinguishes this check from sibling checks such as betriebszustand_zeitbezug_letzte_relevante_nutzung.

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?

It implies the scenario ('längere dokumentierte Nichtnutzung', a stored and unused unit) but gives no explicit when-to-use rule, no prerequisites, and no named alternative for cases that are not long-term storage. An agent must guess at the boundary between this and the other roboter storage/charge checks.

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