Skip to main content
Glama

getecoback-raumklima

pflege_restaufgaben_mit_einem_gesamtstopp

Read-only

Unterbrochene Routine anhand eines erreichbaren, belegt zulässigen Unterbrechungspunkts neu einteilen — Find a permitted stopping point before a household interruption.

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": {
      "teilbarkeit_belegt": "<teilbarkeit_belegt>",
      "vor_stopp_min": "<vor_stopp_min>",
      "danach_min": "<danach_min>",
      "bis_unterbrechung_min": "<bis_unterbrechung_min>",
      "danach_frei_min": "<danach_frei_min>"
    },
    "name": "pflege_restaufgaben_mit_einem_gesamtstopp"
  }
}

Input Schema

NameRequiredDescriptionDefault
danach_minYesAktive Minuten nach Wiederbeginn.
vor_stopp_minYesAktive Minuten vor dem Unterbrechungspunkt.
danach_frei_minYesVerfügbare durchgehende Minuten nach der Unterbrechung.
teilbarkeit_belegtYesSind der Unterbrechungspunkt und die Fortsetzung genau dieses Verfahrens zulässig?
bis_unterbrechung_minYesVerfügbare durchgehende Minuten bis zur Unterbrechung.

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 safety is covered. The description adds almost nothing beyond that: it does not say whether the result is a computed schedule, a feasibility verdict, or what the 'belegt zulässig' precondition implies if the stopping point is not permitted, which is the key behavioral question for this tool.

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?

It is a single sentence with no padding, but the em-dash English restatement largely duplicates the German clause rather than adding clarification, and the key operation is buried at the end of a long noun phrase.

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?

There is no output schema, yet the description never indicates what comes back (a re-partitioned plan, a chosen stopping point, or a yes/no on feasibility), which matters for a five-required-parameter computation tool. The parameter-level documentation is complete, so the gap is confined to result semantics.

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 each of the five parameters carries a German description, so the schema does the heavy lifting. The tool description contributes no additional meaning about units, interactions between 'vor_stopp_min'/'danach_min' and the available windows, so the baseline 3 applies.

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 verb-and-resource pairing ('Unterbrochene Routine ... neu einteilen') and adds the condition 'anhand eines erreichbaren, belegt zulässigen Unterbrechungspunkts', so the agent can tell it is a rescheduling/partitioning operation. However, the phrasing is abstract bureaucratic German and the English addendum ('Find a permitted stopping point') shifts the apparent purpose toward point-finding rather than re-planning, and nothing distinguishes it from the many pflege_* siblings.

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 statement of when to use this versus the dozens of sibling pflege_* tools, no prerequisites, and no exclusions. The only implicit cue is 'vor einer Haushaltsunterbrechung', which hints at the scenario but does not route the agent between alternatives.

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