Skip to main content
Glama

get_scheduled_workout_by_id

Retrieve a scheduled workout's details from a training plan using its unique ID.

Instructions

Get a specific scheduled workout by ID from a training plan

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workoutIdYesThe scheduled workout ID

Implementation Reference

  • Client handler method that makes the HTTP request to the scheduled workout endpoint using the workout ID
    async getScheduledWorkout(workoutId: string): Promise<unknown> {
      return this.request(`${SCHEDULED_WORKOUT_ENDPOINT}/${workoutId}`);
    }
  • Registration of the 'get_scheduled_workout_by_id' tool with the MCP server
    server.registerTool(
      'get_scheduled_workout_by_id',
      {
        description: 'Get a specific scheduled workout by ID from a training plan',
        inputSchema: getScheduledWorkoutSchema.shape,
      },
      async ({ workoutId }) => {
        const data = await client.getScheduledWorkout(workoutId);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Zod input schema for get_scheduled_workout_by_id, validating the required 'workoutId' string
    export const getScheduledWorkoutSchema = z.object({
      workoutId: z.string().describe('The scheduled workout ID'),
    });
  • Endpoint constant for the scheduled workout API path
    export const SCHEDULED_WORKOUT_ENDPOINT = '/workout-service/schedule';
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the retrieval action but does not mention any side effects, data freshness, authentication requirements, or rate limits. For a simple read operation, this is minimal but still lacking context.

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

Conciseness4/5

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

The description is very concise: one sentence with no wasted words. It lacks structure like bullet points or sections, but given the tool's simplicity, it is efficient. However, it could benefit from a more structured format even if short.

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?

For a tool with one parameter and no output schema, the description is minimally adequate. It does not explain what a 'scheduled workout' is relative to a training plan or what the response contains. Given low complexity, a score of 3 reflects that it is functional but could be more informative.

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 fully describes the single parameter 'workoutId' (100% coverage). The description does not add additional meaning beyond the schema's own description. Baseline of 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 clearly states the action ('Get'), the resource ('a specific scheduled workout'), and the scope ('by ID from a training plan'). It distinguishes itself from siblings like 'get_workout' and 'get_workouts' by specifying 'scheduled workout' and 'from a training plan'.

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. With many sibling tools for retrieving workouts and plans, the description should clarify that this is for a scheduled workout within a training plan, but it does not explicitly say when to prefer this over other get methods.

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

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