Skip to main content
Glama

update_recurring_schedule

DestructiveIdempotent

Modify an existing recurring task schedule by changing its title, frequency, assignee, priority, or active status; only supplied fields update and previously created instances remain unchanged.

Instructions

Update an existing recurring task schedule. Change title, description, frequency, assignee, priority, or deactivate it. Only the fields you pass change; instances already created are not edited.

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": {
      "recurring_schedule_id": "<recurring_schedule_id>"
    },
    "name": "update_recurring_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
priorityNoNew priority: urgent, high, medium, low, none.
timezoneNoNew IANA timezone.
cron_exprNoNew cron expression (for custom frequency).
frequencyNoNew frequency: daily, weekly, monthly, custom.
is_activeNoSet to false to pause the schedule.
assignee_idNoNew assignee UUID.
assignee_typeNoNew assignee type: user, agent, unassigned.
title_templateNoNew title template. Supports {{.Date}}, {{.Number}}, {{.Week}}, {{.Month}}.
description_templateNoNew description template. Supports {{.PrevSummary}}.
recurring_schedule_idYesUUID of the recurring schedule to update.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=true; the description adds non-obvious semantics that annotations cannot convey — the update is a partial patch and pre-existing instances are left untouched, plus deactivation is available via a flag. It stops short of explaining what the destructive flag actually destroys (future instance generation) or any permission requirements.

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 short sentences, front-loaded with the action, followed by scope and the one caveat that matters. Nothing is redundant with the schema or wasted.

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 10-parameter, single-required-field mutation with 100% schema coverage and no output schema, the description covers purpose, patch semantics, and side-effect boundaries. Minor gaps remain around return shape and whether the destructive flag implies irreversible loss of pending instances.

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 every parameter (including template placeholders and enum-like value lists) is already documented in the schema. The description only summarizes the field families (title, description, frequency, assignee, priority) and adds no syntax, defaulting, or interaction detail beyond that. Baseline 3 applies when the schema does the heavy lifting.

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?

Opens with a specific verb and resource ("Update an existing recurring task schedule") and immediately enumerates the mutable surface, which cleanly separates it from create_recurring_task, delete_recurring_schedule, and trigger_recurring_now. An agent knows exactly what class of operation this is without opening the schema.

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?

"Only the fields you pass change; instances already created are not edited" gives the agent a decision rule: use this for template-level changes and go elsewhere (e.g. update_task) to touch generated instances. No explicit when-not or named alternative, so it stops short of a 5.

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