Skip to main content
Glama

check_time_reminders

Check for due or upcoming reminders within a specified time window to help users stay on track with scheduled tasks and deadlines.

Instructions

Check for due or upcoming time reminders

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
upcomingMinutesNoCheck for reminders due within this many minutes (default: 60)

Implementation Reference

  • The main handler function for the 'check_time_reminders' tool. It queries the database for due reminders within the specified minutes and returns them as Reminder objects.
    def check_time_reminders(self, upcoming_minutes: int = 60) -> List[Reminder]:
        """Check for due or upcoming time reminders"""
        reminders_data = self.db.get_reminders(upcoming_minutes)
        return [Reminder(**reminder) for reminder in reminders_data]
  • The tool registration block including the input schema definition for 'check_time_reminders'.
        Tool(
            name=TimeTools.CHECK_TIME_REMINDERS.value,
            description="Check for due or upcoming time reminders",
            inputSchema={
                "type": "object",
                "properties": {
                    "upcomingMinutes": {
                        "type": "integer",
                        "description": "Check for reminders due within this many minutes (default: 60)",
                    },
                },
            },
        ),
    ]
  • Dispatch/registration case in the tool execution handler that invokes the check_time_reminders method.
    case TimeTools.CHECK_TIME_REMINDERS.value:
        upcoming_minutes = arguments.get("upcomingMinutes", 60)
        result = time_server.check_time_reminders(upcoming_minutes)
  • Database helper method that implements the core logic for filtering pending reminders due within the upcoming minutes threshold.
    def get_reminders(self, upcoming_minutes: int = 60) -> List[Dict[str, Any]]:
        """Get reminders due within the specified minutes"""
        now = datetime.now(ZoneInfo('UTC'))
        cutoff_time = now + timedelta(minutes=upcoming_minutes)
        
        due_reminders = []
        for reminder in self.reminders:
            if reminder['status'] == 'pending':
                reminder_time = datetime.fromisoformat(reminder['reminderTime'].replace('Z', '+00:00'))
                
                # Fix: Ensure timezone-aware comparison (handles both naive and aware datetimes)
                if reminder_time.tzinfo is None:
                    reminder_time = reminder_time.replace(tzinfo=ZoneInfo('UTC'))
                
                if reminder_time <= cutoff_time:
                    due_reminders.append(reminder)
        
        return due_reminders
  • Pydantic model defining the structure of a Reminder, used as the output type for check_time_reminders.
    class Reminder(BaseModel):
        reminderId: str
        reminderTime: str
        message: str
        relatedTaskId: Optional[str] = None
        status: str  # "pending", "completed"
        createdTime: str
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but lacks critical behavioral details: it doesn't specify whether this is a read-only operation, what permissions might be required, how results are returned (e.g., list format, error handling), or if there are rate limits. For a tool with no annotation coverage, this is a significant gap in transparency.

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 extremely concise and front-loaded, consisting of a single, clear sentence that directly states the tool's purpose. There's no wasted language or redundancy, making it easy for an agent to parse quickly. Every word earns its place by conveying essential information without unnecessary elaboration.

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?

Given the lack of annotations and output schema, the description is incomplete for effective tool use. It doesn't explain what the tool returns (e.g., a list of reminders, success status), error conditions, or behavioral constraints. For a tool that checks data, this omission leaves the agent guessing about the result format and potential side effects, making it inadequate despite the simple parameter schema.

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?

The description adds no parameter-specific information beyond what's already in the input schema, which has 100% coverage for the single parameter 'upcomingMinutes'. The schema fully describes this parameter's purpose, type, and default value. Since the schema does all the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate or add extra semantic context.

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 tool's purpose with a specific verb ('check') and resource ('time reminders'), specifying what it looks for ('due or upcoming'). It distinguishes itself from siblings like 'create_time_reminder' or 'get_current_time' by focusing on checking existing reminders rather than creating or retrieving general time data. However, it doesn't explicitly differentiate from potential overlaps with other reminder-related tools, keeping it from a perfect score.

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, such as needing existing reminders to check, or compare it to sibling tools like 'get_activity_logs' which might also involve time tracking. There's no explicit when-to-use or when-not-to-use context, leaving the agent to infer usage based on the tool name alone.

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