Skip to main content
Glama
AnByoungHyun

Google Calendar MCP

by AnByoungHyun

list_day_events

Retrieve a detailed list of all events scheduled for a specific date (YYYY-MM-DD) on Google Calendar through the MCP protocol.

Instructions

지정한 날짜(YYYY-MM-DD)의 모든 일정 목록 조회

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes

Implementation Reference

  • The handler function for the 'list_day_events' tool, decorated with @mcp.tool(), which fetches events for a specific date from Google Calendar.
    @mcp.tool()
    def list_day_events(date: str) -> dict[str, Any]:
        """지정한 날짜(YYYY-MM-DD)의 모든 일정 목록 조회"""
        service = get_calendar_service()
        start_date = datetime.strptime(date, "%Y-%m-%d")
        end_date = start_date + timedelta(days=1)
        time_min = start_date.isoformat() + 'Z'
        time_max = end_date.isoformat() + 'Z'
        events_result = service.events().list(
            calendarId='primary',
            timeMin=time_min,
            timeMax=time_max,
            singleEvents=True,
            orderBy='startTime'
        ).execute()
        events = events_result.get('items', [])
        return {"count": len(events), "events": events}
  • Supporting helper function that handles Google OAuth authentication and returns the Calendar API service instance, imported and used in the handler.
    def get_calendar_service():
        creds = None
        if os.path.exists(TOKEN_FILE):
            with open(TOKEN_FILE, "rb") as token:
                creds = pickle.load(token)
        if not creds or not creds.valid:
            if creds and creds.expired and creds.refresh_token:
                creds.refresh(Request())
            else:
                flow = InstalledAppFlow.from_client_secrets_file(CLIENT_SECRET_FILE, SCOPES)
                creds = flow.run_local_server(port=0)
            with open(TOKEN_FILE, "wb") as token:
                pickle.dump(creds, token)
        service = build("calendar", "v3", credentials=creds)
        return service 
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 describes a read operation ('조회' means retrieve/look up), implying it's non-destructive, but doesn't specify permissions, rate limits, pagination, or error handling. For a tool with zero annotation coverage, this leaves significant behavioral gaps unaddressed.

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 directly states the tool's function. It's front-loaded with the core purpose and includes the parameter format without unnecessary details. Every word earns its place, making it highly concise and well-structured.

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 tool's moderate complexity (listing events for a date), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions or pagination, doesn't guide usage relative to siblings, and leaves output format unspecified. For a tool with no structured support, more context is needed for effective 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?

The description adds minimal meaning beyond the input schema. It specifies that the 'date' parameter should be in 'YYYY-MM-DD' format, which is useful since schema description coverage is 0%. However, it doesn't explain what constitutes a valid date range, timezone handling, or other constraints. With only one parameter and low schema coverage, this provides some but incomplete compensation.

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: '지정한 날짜(YYYY-MM-DD)의 모든 일정 목록 조회' translates to 'Retrieve all schedule lists for a specified date (YYYY-MM-DD)'. It specifies the verb (retrieve/list), resource (schedule/events), and scope (all for a specific date). However, it doesn't explicitly differentiate from sibling 'list_month_events', which is similar but for a month instead of a day.

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 like 'list_month_events' or 'get_event_detail'. It states what it does but doesn't help an agent decide between this and other listing or detail-retrieval tools. There are no usage conditions, prerequisites, or exclusions mentioned.

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

Related 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/AnByoungHyun/google_calendar_mcp'

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