Skip to main content
Glama

get_activity

Retrieve the full details of a specific Garmin workout activity using its activity ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activity_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_activity' MCP tool. Takes an activity_id, formats the Garmin API endpoint, and returns the activity data via the Garmin Connect API.
    @mcp.tool
    def get_activity(activity_id: str) -> dict:
        endpoint = GET_ACTIVITY_ENDPOINT.format(activity_id=activity_id)
        return _connectapi(endpoint)
  • The tool is registered via the @mcp.tool decorator on the get_activity function, which automatically registers it with the FastMCP server.
    @mcp.tool
    def get_activity(activity_id: str) -> dict:
        endpoint = GET_ACTIVITY_ENDPOINT.format(activity_id=activity_id)
        return _connectapi(endpoint)
  • The endpoint constant used by get_activity to construct the Garmin API URL for fetching activity details.
    GET_ACTIVITY_ENDPOINT = "/activity-service/activity/{activity_id}"
    GET_ACTIVITY_WEATHER_ENDPOINT = "/activity-service/activity/{activity_id}/weather"
    LIST_ACTIVITIES_ENDPOINT = "/activitylist-service/activities/search/activities"
    CREATE_WORKOUT_ENDPOINT = "/workout-service/workout"
    SCHEDULE_WORKOUT_ENDPOINT = "/workout-service/schedule/{workout_id}"
    CALENDAR_WEEK_ENDPOINT = "/calendar-service/year/{year}/month/{month}/day/{day}/start/{start}"
    CALENDAR_MONTH_ENDPOINT = "/calendar-service/year/{year}/month/{month}"
    
    logging.basicConfig(
        level=logging.INFO,
        format="%(asctime)s - %(levelname)s - %(message)s",
        stream=sys.stderr,
    )
    logger = logging.getLogger(__name__)
    
    mcp = FastMCP(name="GarminWorkoutsMCP")
    _AUTH_LOCK = Lock()
    _AUTH_READY = False
    
    
    def _ensure_authenticated() -> None:
        global _AUTH_READY
    
        if _AUTH_READY:
            return
    
        with _AUTH_LOCK:
            if _AUTH_READY:
                return
    
            email = os.environ.get("GARMIN_EMAIL")
            password = os.environ.get("GARMIN_PASSWORD")
            if email or password:
                if not (email and password):
                    raise RuntimeError(
                        "Garmin credentials are incomplete. Set both GARMIN_EMAIL and GARMIN_PASSWORD."
                    )
                try:
                    garth.login(email, password)
                except Exception as exc:
                    raise RuntimeError(
                        "Failed to authenticate with Garmin using GARMIN_EMAIL and GARMIN_PASSWORD."
                    ) from exc
    
                _AUTH_READY = True
                return
    
            raise RuntimeError(
                "Garmin credentials are required for this tool. Set GARMIN_EMAIL and GARMIN_PASSWORD."
            )
    
    
    def _connectapi(endpoint: str, method: str = "GET", **kwargs) -> dict:
        _ensure_authenticated()
        return garth.connectapi(endpoint, method=method, **kwargs)
  • The helper function that wraps the garth.connectapi call with authentication, used by get_activity to make the actual API request.
    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