Skip to main content
Glama

get_activity_weather

Retrieve weather conditions for a specific Garmin activity by providing its activity ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activity_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual tool handler function for 'get_activity_weather'. It takes an activity_id, formats the Garmin weather endpoint URL, and calls _connectapi to fetch the data.
    @mcp.tool
    def get_activity_weather(activity_id: str) -> dict:
        endpoint = GET_ACTIVITY_WEATHER_ENDPOINT.format(activity_id=activity_id)
        return _connectapi(endpoint)
  • The endpoint constant used by get_activity_weather to construct the Garmin API URL for activity weather data.
    GET_ACTIVITY_WEATHER_ENDPOINT = "/activity-service/activity/{activity_id}/weather"
  • The @mcp.tool decorator registers 'get_activity_weather' as an MCP tool on the FastMCP server instance named 'GarminWorkoutsMCP'.
    @mcp.tool
  • The helper function _connectapi used by get_activity_weather to make authenticated API calls to Garmin.
    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