Skip to main content
Glama

list_recurring_schedules

Read-onlyIdempotent

List all project recurring schedules to identify automated task repetitions. Retrieve necessary IDs for managing, updating, triggering, or deleting these schedule entries.

Instructions

Lists the recurring task schedules of a project, with the ids that get_recurring_history, trigger_recurring_now, update_recurring_schedule and delete_recurring_schedule take.

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": {
      "project_id": "<project_id>"
    },
    "name": "list_recurring_schedules"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject UUID, from list_projects.
active_onlyNoDefault true: only active schedules. Pass false to also see paused ones (is_active=false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.6
    • changedInput schema / properties / active_only / description
      Previous value: -"Only return active schedules."New value: +"Default true: only active schedules. Pass false to also see paused ones (is_active=false)."
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID."New value: +"Project UUID, from list_projects."
  2. 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 already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: it tells the agent the return payload's key purpose (the ids consumed by four specific sibling tools), which is the main thing an agent needs to know before calling it.

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?

A single tight sentence that front-loads the action and resource and then names the consumers of the returned ids. No filler or restated title.

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 2-parameter read with full schema coverage and rich annotations but no output schema, the description covers the essential gap—what the returned ids are for. It could say a bit more about returned fields or ordering, but the critical information for correct invocation is present.

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%, with both project_id (UUID, from list_projects) and active_only (default true, false includes paused) fully documented. The description adds no parameter-specific detail beyond the schema, which is the expected baseline when the schema already does the work.

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 (lists) and resource (recurring task schedules of a project), and explicitly names the downstream consumers (get_recurring_history, trigger_recurring_now, update/delete_recurring_schedule). This clearly distinguishes it from siblings like create_recurring_task and get_recurring_history.

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?

The description implies the intended workflow—call this first to obtain ids that the four named siblings require—which is clear contextual guidance. It stops short of explicit 'when not to use' or a named alternative for listing schedules, but for a straightforward list tool the routing signal is strong.

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