Skip to main content
Glama

get-activity-weather

Retrieve weather conditions recorded during a specific activity by providing its activity ID.

Instructions

Get weather conditions during an activity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activityIdYesThe activity ID

Implementation Reference

  • src/tools.ts:245-258 (registration)
    Registration + handler for the get-activity-weather tool. Defined via server.tool() with a Zod schema (activityId: string) and an async handler that calls the Garmin API endpoint activity-service/activity/{activityId}/weather.
    server.tool(
      "get-activity-weather",
      "Get weather conditions during an activity",
      {
        activityId: z.string().describe("The activity ID"),
      },
      async ({ activityId }) => {
        const client = getClient();
        const data = await client.get(
          `activity-service/activity/${activityId}/weather`
        );
        return jsonResult(data);
      }
    );
  • Input schema for get-activity-weather: takes a single required string parameter 'activityId'.
    {
      activityId: z.string().describe("The activity ID"),
    },
  • Handler function that gets a GarminClient via getClient(), makes a GET request to activity-service/activity/{activityId}/weather, and returns the JSON result.
      async ({ activityId }) => {
        const client = getClient();
        const data = await client.get(
          `activity-service/activity/${activityId}/weather`
        );
        return jsonResult(data);
      }
    );
  • Helper function getClient() checks for an existing session, then returns the shared GarminClient instance used by the handler.
    function getClient() {
      if (!sessionExists()) {
        throw new Error(
          "No Garmin session found. The user needs to run: npx garmin-connect-mcp login"
        );
      }
      return getSharedClient();
    }
  • Helper jsonResult() formats the API response as a JSON text content block, used by the handler.
    function jsonResult(data: unknown) {
      return {
        content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }],
      };
    }
Behavior2/5

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

No annotations provided, so description carries full burden. It does not disclose behaviors like error handling (missing activityId), caching, or authentication requirements. Only states the basic function.

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 concise sentence with no unnecessary words. It is front-loaded and effectively communicates the purpose.

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

Completeness3/5

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

Given the simplicity (one parameter) and no output schema, the description is minimally adequate. However, missing behavioral context and lack of output info make it incomplete for confident 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?

Schema description coverage is 100% (one parameter with description 'The activity ID'). The tool description adds no extra meaning beyond what the schema already provides, so baseline 3 is appropriate.

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

Purpose5/5

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

The description 'Get weather conditions during an activity' clearly states the action (Get) and resource (weather conditions for an activity). It distinguishes itself from sibling tools like get-activity, get-activity-details, etc., which focus on other activity attributes.

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?

No guidance on when to use this tool versus alternatives or any prerequisites. The description provides no context about when weather conditions would be needed or when not to use it.

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/etweisberg/garmin-connect-mcp'

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