Skip to main content
Glama

create_time_reminder

Schedule time-based reminders using system time to track tasks and activities. Set reminders with specific times and messages for improved task management and follow-up.

Instructions

Create a time-based reminder using system time for scheduling

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesReminder message
relatedTaskIdNoID of related task or activity
reminderTimeYesTime for the reminder (ISO 8601 format with explicit timezone offset, e.g., '2025-09-11T14:00:00+08:00' for local time or '2025-09-11T14:00:00+00:00' for UTC)

Implementation Reference

  • Core handler function in TimeServer class that executes the tool logic: generates unique ID, validates ISO 8601 reminder time, creates Reminder object, persists to database, and returns the reminder.
    def create_time_reminder(
        self, 
        reminder_time: str, 
        message: str, 
        related_task_id: Optional[str] = None
    ) -> Reminder:
        """Create a time-based reminder"""
        reminder_id = self.id_generator.generate_id()
        created_time = datetime.now(ZoneInfo('UTC')).isoformat(timespec="seconds")
        
        # Validate reminder time format
        try:
            # Handle both 'Z' suffix and existing timezone info
            if reminder_time.endswith('Z'):
                parsed_time = datetime.fromisoformat(reminder_time.replace('Z', '+00:00'))
            else:
                parsed_time = datetime.fromisoformat(reminder_time)
        except ValueError:
            raise ValueError("Invalid reminder time format. Expected ISO 8601 format")
        
        reminder = Reminder(
            reminderId=reminder_id,
            reminderTime=reminder_time,
            message=message,
            relatedTaskId=related_task_id,
            status="pending",
            createdTime=created_time
        )
        
        self.db.add_reminder(reminder)
        return reminder
  • Pydantic model defining the structure of a Reminder, used for output validation and serialization.
    class Reminder(BaseModel):
        reminderId: str
        reminderTime: str
        message: str
        relatedTaskId: Optional[str] = None
        status: str  # "pending", "completed"
        createdTime: str
  • MCP tool registration in list_tools(): defines name, description, and input schema.
    Tool(
        name=TimeTools.CREATE_TIME_REMINDER.value,
        description="Create a time-based reminder using system time for scheduling",
        inputSchema={
            "type": "object",
            "properties": {
                "reminderTime": {
                    "type": "string",
                    "description": "Time for the reminder (ISO 8601 format with explicit timezone offset, e.g., '2025-09-11T14:00:00+08:00' for local time or '2025-09-11T14:00:00+00:00' for UTC)",
                },
                "message": {
                    "type": "string",
                    "description": "Reminder message",
                },
                "relatedTaskId": {
                    "type": "string",
                    "description": "ID of related task or activity",
                },
            },
            "required": ["reminderTime", "message"],
        },
    ),
  • Dispatch logic in _execute_tool() that validates arguments and invokes the handler for create_time_reminder.
    case TimeTools.CREATE_TIME_REMINDER.value:
        if not all(k in arguments for k in ["reminderTime", "message"]):
            raise ValueError("Missing required arguments: reminderTime and message")
    
        result = time_server.create_time_reminder(
            arguments["reminderTime"],
            arguments["message"],
            arguments.get("relatedTaskId"),
        )
  • Enum value defining the tool name constant.
    CREATE_TIME_REMINDER = "create_time_reminder"
    CHECK_TIME_REMINDERS = "check_time_reminders"
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'create' implying a write/mutation operation but doesn't disclose behavioral traits like required permissions, whether reminders are persistent, if they trigger notifications, rate limits, or error conditions. The phrase 'using system time' adds minimal context but leaves key behaviors unspecified for a creation tool.

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 a single, efficient sentence that front-loads the core action ('Create a time-based reminder') with clarifying detail ('using system time for scheduling'). There's zero wasted text, and it directly communicates the tool's function without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with no annotations and no output schema, the description is incomplete. It doesn't cover what happens after creation (e.g., success response, reminder ID), error handling, or system dependencies. The high schema coverage helps with inputs, but behavioral and output aspects are lacking, making it inadequate for safe agent use.

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 all parameters well-documented in the schema (e.g., reminderTime format details). The description adds no parameter-specific semantics beyond the tool's overall purpose. It doesn't explain relationships between parameters or usage nuances, so it meets the baseline for high schema coverage without adding value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('create') and resource ('time-based reminder') with the specific mechanism 'using system time for scheduling'. It distinguishes from siblings like 'check_time_reminders' (read vs. create) and time-related tools like 'get_current_time' (query vs. action). However, it doesn't explicitly differentiate from all siblings like 'start_activity_log' which might also involve time scheduling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when-not-to-use scenarios, or compare to siblings like 'check_time_reminders' for viewing reminders or 'update_activity_log' for modifying time-related entries. Usage is implied by the action 'create' but lacks explicit context.

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/n0zer0d4y/chronos-protocol'

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