Skip to main content
Glama

suggest_meeting_times

Analyze your Google Calendar to find available time slots for scheduling meetings within a specified date range, respecting your existing events and working hours.

Instructions

    Suggest available meeting times within a date range.
    
    This tool analyzes the user's calendar and suggests available time slots
    for scheduling meetings based on their existing calendar events.
    
    Prerequisites:
    - The user must be authenticated with Google Calendar access
    
    Args:
        start_date (str): The start date of the range to check (can be natural language like "tomorrow")
        end_date (str): The end date of the range to check (can be natural language like "next friday")
        duration_minutes (int, optional): The desired meeting duration in minutes. Defaults to 60.
        working_hours (str, optional): Working hours in format "9-17" (9am to 5pm). Defaults to 9am-5pm.
        
    Returns:
        Dict[str, Any]: The suggested meeting times including:
            - success: Whether the operation was successful
            - suggestions: List of suggested meeting times with formatted date/time
            - message: A message describing the result
            
    Example usage:
    1. Find meeting times for tomorrow:
       suggest_meeting_times(start_date="tomorrow", end_date="tomorrow")
       
    2. Find meeting times for next week with custom duration:
       suggest_meeting_times(
           start_date="next monday", 
           end_date="next friday", 
           duration_minutes=30
       )
       
    3. Find meeting times with custom working hours:
       suggest_meeting_times(
           start_date="tomorrow", 
           end_date="friday", 
           working_hours="10-16"
       )
       
    Important:
    - The tool respects the user's existing calendar events
    - Suggestions are limited to working hours (default 9am-5pm)
    - Weekends are excluded by default
    - The tool will return at most 10 suggestions
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_dateYes
end_dateYes
duration_minutesNo
working_hoursNo
Behavior4/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 does an excellent job describing key behavioral traits: it respects existing calendar events, limits suggestions to working hours (default 9am-5pm), excludes weekends by default, returns at most 10 suggestions, and requires authentication. The only minor gap is not mentioning potential rate limits or error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (purpose, prerequisites, args, returns, examples, important notes) and every sentence adds value. It's slightly longer than ideal but efficiently conveys necessary information. The front-loaded purpose statement is excellent, though some redundancy exists between the initial description and later elaboration.

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?

Given the tool's complexity (calendar analysis with multiple parameters) and the absence of both annotations and output schema, the description provides complete context. It covers authentication requirements, behavioral constraints, parameter details, return value structure, and practical examples. This is comprehensive enough for an agent to understand and use the tool effectively.

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?

With 0% schema description coverage, the description fully compensates by providing detailed parameter semantics. It explains each parameter's purpose, format expectations (natural language for dates, '9-17' format for working hours), default values, and optional status. The examples further clarify how to use the parameters in practice.

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 the tool's purpose: 'Suggest available meeting times within a date range' and elaborates that it 'analyzes the user's calendar and suggests available time slots for scheduling meetings based on their existing calendar events.' This is a specific verb+resource combination that distinguishes it from sibling tools like 'list_calendar_events' or 'create_calendar_event'.

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 provides clear context about when to use this tool (for finding available meeting times based on calendar analysis) and includes prerequisites (Google Calendar authentication). However, it doesn't explicitly state when NOT to use it or mention specific alternatives among the sibling tools, such as when to use 'list_calendar_events' instead.

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/bastienchabal/gmail-mcp'

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