Skip to main content
Glama
cronty-com

Cronty MCP

Official
by cronty-com

schedule_cron_notification

Schedule recurring notifications using cron syntax with timezone and topic configuration. Send notification messages persistently via Upstash until deleted.

Instructions

Schedule a recurring notification using cron syntax.

Creates a persistent schedule that fires according to the cron pattern. The schedule continues indefinitely until deleted via the Upstash panel.

The agent should determine the user's timezone by:

  1. Checking system/environment timezone information

  2. If unavailable, asking the user explicitly

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cronYesStandard 5-field cron expression. Fields: minute hour day-of-month month day-of-week. Examples: '0 9 * * 1' (Mondays 9am), '30 8 * * 1-5' (weekdays 8:30am), '0 0 1 * *' (monthly)
labelNoOptional label for identifying this schedule in the Upstash dashboard logs. Only alphanumeric, hyphen, underscore, or period allowed. Examples: 'daily-standup', 'weekly_report', 'reminder.v1'
messageYesThe notification text to send
timezoneYesIANA timezone for the cron schedule. Check the user's system timezone first. If unavailable, ask the user for their timezone. Examples: Europe/Warsaw, Europe/London, America/New_York, America/Los_Angeles, Asia/Tokyo, Asia/Shanghai, Australia/Sydney, UTC
notification_topicYesThe notification topic to send to. Format: lowercase alphanumeric with dashes (e.g., 'my-alerts', 'user-123-notifications')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries behavioral disclosure burden. It explains persistence and indefinite continuation until manual deletion, but does not cover failure modes, rate limits, or delivery confirmation.

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?

Description is front-loaded with the core purpose, followed by concise behavioral and usage details. Each sentence adds value with no redundancy.

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?

Covers main behavioral points (persistence, timezone handling) and parameter details. Lacks return value explanation, but output schema exists. Adequate for a scheduling tool with good schema coverage.

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 descriptions cover 100% of parameters, and the description adds extra value with cron examples, label format rules, and timezone examples. The timezone determination procedure is also explained, going beyond bare schema.

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?

Name and description clearly state the tool's action: scheduling a recurring notification using cron syntax. It distinguishes from siblings like schedule_notification (likely one-time) and send_push_notification (immediate) by specifying recurring nature.

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?

Description provides explicit guidance on timezone determination (check system, then ask user) and notes that schedules persist until deleted. While it doesn't explicitly contrast with one-time scheduling, the context implies when to use this tool over alternatives.

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/cronty-com/cronty-mcp'

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