Skip to main content
Glama

Move tasks to another day

move_tasks

Move all tasks from one day to another, e.g. "move today's unfinished tasks to tomorrow". By default only unfinished tasks move; repeating occurrences that have not been opened in the app stay on their schedule. To move specific tasks use update_tasks. If this would move more than a few tasks and the user did not clearly ask for it, confirm with the user first. One undo_last_change moves them all back.

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": {
      "fromDayKey": "<fromDayKey>",
      "toDayKey": "<toDayKey>"
    },
    "name": "move_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
onlyOpenNotrue (default) = only unfinished tasks; false = also move completed ones.
toDayKeyYesDay to move them to ("YYYY-MM-DD", "tomorrow").
fromDayKeyYesDay to move tasks from ("YYYY-MM-DD", "today", "yesterday").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare the write profile (readOnlyHint=false, destructiveHint=false, non-idempotent), and the description adds real behavior beyond them: the default only moves unfinished tasks, unopened repeating occurrences stay on schedule, and one undo_last_change reverses the whole batch. It stops short of describing what the call returns or how large a batch realistically is.

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 core action and example, then escalating to the alternative and the safety warning. Every sentence carries information; the only slight redundancy is restating the unfinished-only default that the schema already declares.

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

Completeness4/5

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

For a three-parameter bulk mutation with no output schema, the description covers defaults, side effects, reversibility, and a confirmation guardrail, which is sufficient to call it safely. What moved in the response is left implicit, which is a minor 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 coverage is 100%, so all three parameters are already documented including the onlyOpen default and day-key formats. The description corroborates the unfinished-only default and adds the repeating-occurrence nuance, but contributes no format or syntax detail the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with scope: "Move all tasks from one day to another", with a concrete example. It also explicitly routes narrow cases to update_tasks, so the agent can distinguish it from siblings without reading either schema.

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

Usage Guidelines5/5

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

Names the alternative (update_tasks) and the condition that selects it (moving specific tasks), plus a confirmation precondition for large bulk moves the user didn't clearly request. That is explicit when-to-use, when-to-defer, and when-to-confirm guidance.

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