Skip to main content
Glama

get_calendar

Retrieve workout calendar entries for a specified year and month. Optionally filter by day for detailed view.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYes
monthYes
dayNo
startNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The @mcp.tool decorated handler function for 'get_calendar'. Takes year, month, optional day, and start params, validates them, and calls the Garmin calendar API (month or week view).
    @mcp.tool
    def get_calendar(year: int, month: int, day: int | None = None, start: int = 1) -> dict:
        if not 1900 <= year <= 2100:
            raise ValueError(f"Year must be between 1900 and 2100, got {year}")
        if not 1 <= month <= 12:
            raise ValueError(f"Month must be between 1 and 12, got {month}")
        if day is not None and not 1 <= day <= 31:
            raise ValueError(f"Day must be between 1 and 31, got {day}")
    
        garmin_month = month - 1
        if day is None:
            endpoint = CALENDAR_MONTH_ENDPOINT.format(year=year, month=garmin_month)
            view_type = "month"
        else:
            endpoint = CALENDAR_WEEK_ENDPOINT.format(year=year, month=garmin_month, day=day, start=start)
            view_type = "week"
    
        return {
            "calendar": _connectapi(endpoint),
            "view_type": view_type,
            "period": {"year": year, "month": month, "day": day, "start": start if day else None},
        }
  • Type hints define the input schema: year (int), month (int), optional day (int|None), start (int with default 1). Return type is dict.
    def get_calendar(year: int, month: int, day: int | None = None, start: int = 1) -> dict:
  • The @mcp.tool decorator registers 'get_calendar' as an MCP tool with the FastMCP server instance 'mcp'.
    @mcp.tool
  • Endpoint constants used by get_calendar: CALENDAR_WEEK_ENDPOINT and CALENDAR_MONTH_ENDPOINT for the Garmin calendar-service API.
    CALENDAR_WEEK_ENDPOINT = "/calendar-service/year/{year}/month/{month}/day/{day}/start/{start}"
    CALENDAR_MONTH_ENDPOINT = "/calendar-service/year/{year}/month/{month}"
  • The _connectapi helper function that wraps garth.connectapi, ensuring authentication before making the actual API call.
    def _connectapi(endpoint: str, method: str = "GET", **kwargs) -> dict:
        _ensure_authenticated()
        return garth.connectapi(endpoint, method=method, **kwargs)
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/pranciskus/garmin-workouts-mcp'

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