Skip to main content
Glama

Add repeating task

add_repeating_task

Create a task that repeats every day or every week, e.g. "gym every Monday at 18:00" or "take vitamins daily". Weekly tasks repeat on the weekday of startDayKey (or pass weekday to start on the first such day on or after startDayKey). Don't also add the days with add_tasks; the app shows every occurrence. Can be reverted with undo_last_change.

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": {
      "title": "<title>",
      "repeat": "<repeat>",
      "startDayKey": "<startDayKey>"
    },
    "name": "add_repeating_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesShort task text.
repeatYes
weekdayNoWeekly only: the day of the week it repeats on.
endDayKeyNoLast day it may happen (inclusive). Omit to repeat forever.
reminderAtNoReminder at "HH:MM" on each occurrence's day (works without a time). Use instead of reminderMinutesBefore.
startDayKeyYesFirst day of the series.
timeMinutesNoStart time as minutes after midnight, 0-1439 (e.g. 9:30 → 570, 18:00 → 1080). Omit for an all-day task.
reminderMinutesBeforeNoPhone reminder this many minutes before the start time (0 = at the start time). Requires a time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description only needs to add context — and it does: recurrence expansion semantics, the warning that occurrences should not be duplicated via add_tasks, and the undo_last_change escape hatch. It stops short of saying that calling it twice with the same title creates two series, which is the one non-idempotency consequence worth spelling out.

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

Conciseness5/5

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

Three sentences, front-loaded with the purpose before the recurrence rules and the add_tasks exclusion. Every clause carries information — the examples disambiguate format, the parenthetical resolves an edge case, and the undo note sets expectations. Nothing is padded.

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 an 8-parameter mutation with no output schema, the description covers the hard parts: recurrence semantics, occurrence duplication, and revertibility. It does not say what the call returns (a task or series identifier) or how the series surfaces in list_repeating_tasks, which would help the agent chain follow-up calls, but the core invocation is unambiguous.

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

Parameters4/5

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

Schema coverage is 88%, so baseline is 3; the description earns an extra point by explaining the interaction the schema cannot: weekly tasks default to the weekday of startDayKey, and passing weekday shifts the first occurrence to the first such day on or after startDayKey. That is genuine cross-parameter semantics, not a restatement of field docs.

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 ("Create a task that repeats every day or every week") and grounds it with two concrete examples ("gym every Monday at 18:00", "take vitamins daily"). It also names the sibling it is not — add_tasks — so the agent can distinguish the recurring-task path from the one-off path without opening 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?

Gives an explicit when-not: "Don't also add the days with add_tasks; the app shows every occurrence," which is exactly the mistake an agent would otherwise make. It also states a recovery path ("Can be reverted with undo_last_change") and clarifies the weekday vs startDayKey selection rule, so the calling context is fully framed.

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