Skip to main content
Glama

get_workout

Retrieve complete workout summary including laps, heart rate zones, training effect, and sport-specific metrics. Use after listing workouts to get full details.

Instructions

Returns the full summary for one workout: all fields Suunto exposes including laps, HR zones, training-effect score, and sport-specific metrics (pace zones for running, power for cycling, etc.). Throws SuuntoNotFoundError if the workoutKey does not exist. Use list_workouts to discover valid workoutKey values. For second-by-second time-series (HR, pace, GPS) use get_workout_samples instead. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workoutKeyYesOpaque server-assigned string returned by list_workouts. Not guessable or constructable — always discover via list_workouts first. Passing an invalid key throws SuuntoNotFoundError.

Implementation Reference

  • src/index.ts:82-97 (registration)
    Tool registration: defines the 'get_workout' tool with name, description, and inputSchema (requiring workoutKey string).
    {
      name: "get_workout",
      description:
        "Returns the full summary for one workout: all fields Suunto exposes including laps, HR zones, training-effect score, and sport-specific metrics (pace zones for running, power for cycling, etc.). Throws SuuntoNotFoundError if the workoutKey does not exist. Use list_workouts to discover valid workoutKey values. For second-by-second time-series (HR, pace, GPS) use get_workout_samples instead. Read-only.",
      inputSchema: {
        type: "object",
        properties: {
          workoutKey: {
            type: "string",
            minLength: 1,
            description: "Opaque server-assigned string returned by list_workouts. Not guessable or constructable — always discover via list_workouts first. Passing an invalid key throws SuuntoNotFoundError.",
          },
        },
        required: ["workoutKey"],
      },
    },
  • Input schema for get_workout: requires 'workoutKey' (string, minLength 1).
    inputSchema: {
      type: "object",
      properties: {
        workoutKey: {
          type: "string",
          minLength: 1,
          description: "Opaque server-assigned string returned by list_workouts. Not guessable or constructable — always discover via list_workouts first. Passing an invalid key throws SuuntoNotFoundError.",
        },
      },
      required: ["workoutKey"],
    },
  • Handler for get_workout: calls suunto.getWorkout(a.workoutKey) and returns JSON result.
    case "get_workout": {
      const data = await suunto.getWorkout(a.workoutKey);
      return text(JSON.stringify(data));
    }
  • API helper method getWorkout: calls Suunto API endpoint /v2/workout/{workoutKey} and returns parsed JSON.
    getWorkout(workoutKey: string) {
      return this.json<any>(`/v2/workout/${encodeURIComponent(workoutKey)}`);
    }
  • src/cli.ts:73-77 (registration)
    CLI handler for 'get-workout' command (dash variant), calls suunto.getWorkout(key).
    case "get-workout": {
      const key = rest[0] ?? die("Usage: get-workout <workoutKey>");
      out(await suunto.getWorkout(key));
      break;
    }
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that it throws SuuntoNotFoundError for invalid keys and states it is read-only. It does not mention rate limits or other constraints, but for a simple get operation, this is sufficient.

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 two focused sentences with no wasted words. It front-loads the main purpose and immediately follows with error behavior and sibling alternatives.

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

Completeness4/5

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

Given the simple interface (one parameter, no output schema), the description covers the primary functionality, error handling, and relationship to sibling tools. It could potentially mention response format, but the absence of output schema reduces the need.

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?

The input schema already provides a detailed description for workoutKey (opaque, not guessable, discover via list_workouts, error on invalid). The tool description reinforces this by mentioning the error, but does not add new semantic meaning beyond the schema.

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 specifies exactly what the tool returns: full summary for one workout with fields like laps, HR zones, training-effect score, and sport-specific metrics. It distinguishes itself from sibling get_workout_samples by noting that tool provides time-series data.

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

Usage Guidelines5/5

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

It explicitly tells the agent to use list_workouts to discover valid workoutKey values, and advises using get_workout_samples for time-series data. This provides clear guidance on when to use this tool versus alternatives.

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/googlarz/suunto-mcp'

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