Skip to main content
Glama

get_devices

Retrieve registered Garmin devices and their details including model, firmware version, and last sync timestamp.

Instructions

Get all registered Garmin devices: model, firmware, last sync

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual implementation of getDevices - makes an HTTP request to the Garmin API endpoint to fetch all registered devices.
    async getDevices(): Promise<unknown> {
      return this.request(DEVICE_LIST_ENDPOINT);
  • Registration of the 'get_devices' tool on the MCP server with description and handler that calls client.getDevices().
    server.registerTool(
      'get_devices',
      {
        description: 'Get all registered Garmin devices: model, firmware, last sync',
      },
      async () => {
        const data = await client.getDevices();
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • The API endpoint constant for the device list used by the getDevices handler.
    export const DEVICE_LIST_ENDPOINT = '/device-service/deviceregistration/devices';
  • Registration function that registers all profile-related tools including 'get_devices'.
    export function registerProfileTools(server: McpServer, client: GarminClient): void {
      server.registerTool(
        'get_user_profile',
        {
          description: 'Get user social profile: name, location, profile image, activity preferences, level',
        },
        async () => {
          const data = await client.getUserProfile();
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    
      server.registerTool(
        'get_user_settings',
        {
          description:
            'Get user settings: measurement system, time/date format, sleep schedule, HR zones, hydration preferences',
        },
        async () => {
          const data = await client.getUserSettings();
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    
      server.registerTool(
        'get_devices',
        {
          description: 'Get all registered Garmin devices: model, firmware, last sync',
        },
        async () => {
          const data = await client.getDevices();
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    
      server.registerTool(
        'get_device_settings',
        {
          description: 'Get settings and configuration for a specific Garmin device',
          inputSchema: getDeviceSettingsSchema.shape,
        },
        async ({ deviceId }) => {
          const data = await client.getDeviceSettings(deviceId);
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    
      server.registerTool(
        'get_device_last_used',
        {
          description: 'Get the last used Garmin device info',
        },
        async () => {
          const data = await client.getDeviceLastUsed();
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    
      server.registerTool(
        'get_primary_training_device',
        {
          description: 'Get the primary training device info',
        },
        async () => {
          const data = await client.getPrimaryTrainingDevice();
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    
      server.registerTool(
        'get_device_solar_data',
        {
          description: 'Get solar charging data for solar-equipped Garmin devices',
          inputSchema: getDeviceSolarSchema.shape,
        },
        async ({ deviceId, startDate, endDate }) => {
          const data = await client.getDeviceSolarData(deviceId, startDate, endDate);
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    
      server.registerTool(
        'get_gear',
        {
          description: 'Get all gear/equipment: shoes, bikes, and other tracked equipment',
        },
        async () => {
          const data = await client.getGear();
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    
      server.registerTool(
        'get_gear_stats',
        {
          description: 'Get usage statistics for a specific gear item (total distance, activities)',
          inputSchema: getGearStatsSchema.shape,
        },
        async ({ gearUuid }) => {
          const data = await client.getGearStats(gearUuid);
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    
      server.registerTool(
        'get_goals',
        {
          description: 'Get active goals: step goals, activity goals, weight goals, and their progress',
        },
        async () => {
          const data = await client.getGoals();
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    
      server.registerTool(
        'get_earned_badges',
        {
          description: 'Get all earned badges and achievements',
        },
        async () => {
          const data = await client.getEarnedBadges();
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    
      server.registerTool(
        'get_workouts',
        {
          description: 'Get saved workouts/training plans',
        },
        async () => {
          const data = await client.getWorkouts();
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    
      server.registerTool(
        'get_workout',
        {
          description: 'Get a specific workout definition by ID',
          inputSchema: getWorkoutSchema.shape,
        },
        async ({ workoutId }) => {
          const data = await client.getWorkout(workoutId);
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    
      server.registerTool(
        'get_gear_activities',
        {
          description: 'Get activities associated with a specific gear item (e.g. runs with a specific pair of shoes)',
          inputSchema: getGearActivitiesSchema.shape,
        },
        async ({ gearUuid, start, limit }) => {
          const data = await client.getGearActivities(gearUuid, start ?? 0, limit ?? 20);
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    
      server.registerTool(
        'get_gear_defaults',
        {
          description: 'Get default gear assignments per activity type',
        },
        async () => {
          const data = await client.getGearDefaults();
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    }
Behavior3/5

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

As a zero-parameter read operation, the description is fairly transparent. However, with no annotations, it could better disclose potential pagination, data freshness, or device status (registered vs. inactive).

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?

Single sentence, front-loaded with verb, no wasted words. Perfectly concise.

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?

For a simple list tool with no parameters and no output schema, the description covers the essential return fields. Lacks details on sorting or pagination, but adequate given low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No input parameters exist, so baseline 4 applies. The description adds no parameter meaning but lists output fields, which is beyond the empty 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 clearly states the action ('Get all registered Garmin devices') and specifies the returned fields (model, firmware, last sync). It distinguishes itself from sibling tools like get_device_settings (specific device) and get_device_last_used (last used time).

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 explicit guidance on when to use or avoid this tool. While the name and description imply it's for a broad list, there is no mention of alternatives like get_device_settings for detailed info on a single device.

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