Skip to main content
Glama
AnByoungHyun

Google Calendar MCP

by AnByoungHyun

list_month_events

Retrieve a complete list of all events for a specified year and month from Google Calendar using natural language commands with OAuth2 authentication.

Instructions

지정한 연/월의 모든 일정 목록 조회

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monthYes
yearYes

Implementation Reference

  • Handler function for 'list_month_events' tool. Queries Google Calendar API for all events in the specified year and month, returns count and list of events.
    @mcp.tool()
    def list_month_events(year: int, month: int) -> dict[str, Any]:
        """지정한 연/월의 모든 일정 목록 조회"""
        service = get_calendar_service()
        start_date = datetime(year, month, 1)
        if month == 12:
            end_date = datetime(year + 1, 1, 1)
        else:
            end_date = datetime(year, month + 1, 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}
  • The @mcp.tool() decorator registers the list_month_events function as an MCP tool.
    @mcp.tool()
  • Helper utility to obtain an authenticated Google Calendar service instance, used by the tool 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 full burden but offers minimal behavioral insight. It implies a read-only operation ('조회') but doesn't disclose permissions, rate limits, pagination, error handling, or what '모든' (all) entails (e.g., completeness guarantees). More context is needed for safe use.

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 in Korean with zero wasted words. It's front-loaded with the core action and scope, making it easy to parse despite its brevity.

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 no annotations, 0% schema coverage, no output schema, and sibling tools, the description is incomplete. It lacks details on behavior, parameters, output format, and differentiation from alternatives, making it inadequate for reliable tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate but adds no parameter details. It mentions '지정한 연/월' (specified year/month), hinting at 'year' and 'month' parameters, but provides no semantics on formats, constraints, or interactions. This leaves parameters largely undocumented.

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 as '조회' (retrieve/query) for '일정 목록' (event list) within a '지정한 연/월' (specified year/month). It uses a specific verb and resource, though it doesn't explicitly differentiate from sibling 'list_day_events' beyond the time scope.

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_day_events' or 'get_event_detail'. It mentions the time scope (year/month) but doesn't clarify use cases, prerequisites, or exclusions relative to siblings.

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