classdesk

Termin verschieben

shift_calendar_event

Verschiebt einen Termin samt dem, was daran hängt (verknüpfte Vorbereitungs-Karten, Countdowns auf Bildschirmen, Termine derselben Klasse am selben Tag). key aus list_calendar (z. B. "own:12", "task:5", "parents:3") oder event_id. Ohne confirm: Vorschau – related (checked = würde mitwandern), on_new_date (was dort schon ist, Ferien zuerst), weekend. Mit confirm=true verschieben: keys = mitwandernde Einträge (Standard: die mit checked).

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": {
      "date": "<date>"
    },
    "name": "shift_calendar_event"
  }
}

Input Schema

Name	Required	Description
`key`	No
`date`	Yes	Neues Datum JJJJ-MM-TT
`keys`	No
`confirm`	No
`event_id`	No	Statt key: eigener Termin

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the thin annotations by disclosing the cascade (related cards, countdowns, same-class events travel along) and the preview/confirm two-step. It does not say whether the move is reversible (undo_change exists as a sibling) or what permissions are needed, which keeps it from a 5.

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?

Front-loaded with the effect and cascade, then the preview/execute split, then parameter details. Dense but nearly every clause carries information; the parenthetical enumerations are long but justified.

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

Completeness5/5

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

With no output schema, the description still documents the preview payload (related with checked flags, on_new_date with holidays first, weekend), so an agent can interpret the response without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Compensates for 40% schema coverage: key gets format examples ("own:12", "task:5", "parents:3") and a source tool, keys gets a documented default (the entries marked checked), and confirm's two modes are spelled out. Only date duplicates the schema, which already documents the JJJJ-MM-TT format.

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?

States a specific verb and resource plus its cascade scope: moving an event together with linked prep cards, screen countdowns, and same-class events. An agent knows exactly what will happen, but the description never names the sibling it must not confuse with (update_calendar_event / prepare_calendar_event), so sibling differentiation is only implicit.

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?

Clear operational guidance: without confirm it is a preview, with confirm=true it executes, and the key is sourced from list_calendar. Missing an explicit exclusion against the update/prepare/delete calendar siblings, which matters given how many calendar tools exist.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All classdesk tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?