Skip to main content
Glama

getecoback-raumklima

pflegeabschluss_zwei_quittungen_vorzeitigkeit

Read-only

Zwei dokumentierte Abschlüsse darauf prüfen, ob die Quittung zum richtigen Arbeitsschritt gehört — Detect close-out notes timestamped before their own work could finish.

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": {
      "gleiche_runde": "<gleiche_runde>",
      "erster_start": "<erster_start>",
      "erster_dauer": "<erster_dauer>",
      "erster_quittiert": "<erster_quittiert>",
      "zweiter_start": "<zweiter_start>",
      "zweiter_dauer": "<zweiter_dauer>",
      "zweiter_quittiert": "<zweiter_quittiert>"
    },
    "name": "pflegeabschluss_zwei_quittungen_vorzeitigkeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
erster_dauerYesTatsächliche Dauer des ersten Schritts.
erster_startYesStart des ersten Arbeitsschritts.
gleiche_rundeYesSind Uhr und zwei Arbeitsschritte in der tatsächlich protokollierten Reihenfolge eindeutig zugeordnet?
zweiter_dauerYesTatsächliche Dauer des zweiten Schritts.
zweiter_startYesStart des zweiten Arbeitsschritts.
erster_quittiertYesTagesminute des zugehörigen ersten Häkchens.
zweiter_quittiertYesTagesminute des zugehörigen zweiten Häkchens.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 the safety profile is covered. The description adds the core behavioral idea that the check compares receipt timestamps against the feasible completion of the work, but says nothing about the shape of the verdict, what happens when 'gleiche_runde' is false, or whether the two steps are checked jointly or independently.

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 short and front-loaded, but the same content is restated in German and English rather than the second half extending the first, and the two clauses emphasize slightly different checks. No wasted sentences, but the bilingual duplication costs more than it clarifies.

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?

Seven required parameters, no output schema, and the description says nothing about the return value of a verification tool — an agent cannot tell whether it receives a boolean, a list of anomalies, or a corrected assignment. For a multi-parameter validation tool with no output schema, this leaves a material gap.

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 seven parameters carries its own German description, including the range 0–1440 for minute values. The description adds no parameter-level meaning beyond that; notably it never mentions the 'gleiche_runde' gate that determines whether the comparison is even valid. Baseline 3 is appropriate.

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 operation on a specific resource: checking two documented close-outs for whether a receipt/sign-off timestamp precedes the completion of its own work step. The English clause ('Detect close-out notes timestamped before their own work could finish') disambiguates the vaguer German phrasing about 'the right work step'. It is distinguishable from the sibling list, none of which appear to be a premature-sign-off validator, though the two language halves are not perfectly aligned in meaning.

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 call this versus alternatives, no prerequisites (e.g. that the two steps must be from the same round), and no mention of what a negative or ambiguous result means. The only implicit guidance is that you need two closed-out steps with start, duration and receipt times.

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