Skip to main content
Glama
cronty-com

Cronty MCP

Official
by cronty-com

schedule_notification

Schedule a one-off notification to be sent at a future date and time. Supports ISO 8601, date+time+timezone, or delay formats.

Instructions

Schedule a one-off notification for a future time.

Supports three input modes (use only one):

  1. datetime: ISO 8601 format (e.g., 2025-01-15T09:00:00+01:00)

  2. date + time + timezone: Separate parameters

  3. delay: QStash delay format (e.g., 1d, 2h30m, 1d10h30m50s)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format. Defaults to today if omitted.
timeNoTime in HH:MM format
delayNoQStash delay format (e.g., "1d", "2h30m", "1d10h30m")
messageYesThe notification text to send
datetimeNoISO 8601 datetime with timezone
timezoneNoIANA timezone (required with date+time). 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

Behavior3/5

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

No annotations provided, so description carries full burden. Details input modes and formats but does not disclose success/failure behavior, side effects, or required permissions. Adequate but could be more transparent.

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?

Concise, well-structured with bullet points. Front-loads purpose then details modes. Every sentence adds value. No wasted words.

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?

Output schema exists, so return values are documented elsewhere. Covers all 7 parameters, explains exclusive modes, and provides necessary format details. Minor gaps like max delay duration, but overall complete for the tool's complexity.

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 description coverage is 100%, baseline 3. Description adds significant value by grouping parameters into modes, clarifying exclusivity, and providing format examples (ISO 8601, QStash delay).

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?

Clearly states 'Schedule a one-off notification for a future time.' Specifies verb, resource, and time constraint. Distinguishes from siblings like schedule_cron_notification (recurring) and send_push_notification (immediate).

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?

Explicitly describes three input modes and states 'use only one.' Provides format examples. Agent can infer when to use this vs. siblings (cron for recurring, send_push for immediate). Lacks explicit exclusions but clear enough.

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