Skip to main content
Glama

build_recurrence_rule

Build an iCalendar RRULE string to define recurrence rules for tasks and habits. Configure frequency, interval, days, count, or end date.

Instructions

Build an iCalendar RRULE string for recurring tasks or habits.

[Category: Utilities]  [Auth: none]
[Related: create_task, update_task, create_habit]

Args:
    frequency: "DAILY", "WEEKLY", "MONTHLY", or "YEARLY".
    interval: Repeat every N units (default 1).
    by_day: Weekday codes for WEEKLY, e.g. ["MO","WE","FR"].
    by_month_day: Day of month (1-31) for MONTHLY.
    by_month: Month number (1-12) for YEARLY.
    count: End after N occurrences.
    until: End date UTC: "20261231T000000Z".

Examples:
    Every day          → frequency="DAILY"
    Mon/Wed/Fri        → frequency="WEEKLY", by_day=["MO","WE","FR"]
    15th of each month → frequency="MONTHLY", by_month_day=15
    Every 2 weeks      → frequency="WEEKLY", interval=2
    3 times then stop  → frequency="DAILY", count=3

Returns {"rrule": "RRULE:FREQ=..."} — pass the rrule value as the
'recurrence' parameter in create_task/update_task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frequencyYes
intervalNo
by_dayNo
by_month_dayNo
by_monthNo
countNo
untilNo
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the return format ({'rrule': ...}) and that no authentication is needed (Auth: none). It does not mention any side effects, but for a utility tool that builds a string, this is adequate.

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?

The description is well-structured with categories, args list, examples, and return info. Every sentence adds value, and it is concise without being terse.

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?

The description fully explains the tool's purpose, parameters, return value, and how to use the output. Given the tool's simplicity and the absence of an output schema, it is complete.

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?

Schema description coverage is 0%, so the description must compensate. It does so by listing all 7 parameters with explanations and examples, adding significant meaning beyond the schema titles.

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?

The description clearly states it builds an iCalendar RRULE string for recurring tasks or habits, which is a specific verb+resource. It distinguishes itself from siblings by mentioning related tools like create_task and update_task, and explains how the output is used.

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 implicitly guides usage by explaining the output is to be passed as the 'recurrence' parameter in create_task/update_task, and includes examples. However, it does not explicitly state when not to use it or alternatives, but given the utility nature, it's clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/KpihX/tick-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server