Skip to main content
Glama

get_device_settings

Retrieve settings and configuration for any Garmin device using its device ID. Access device-specific options and preferences from Garmin Connect.

Instructions

Get settings and configuration for a specific Garmin device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceIdYesThe Garmin device ID

Implementation Reference

  • Client handler that performs the HTTP request to fetch device settings from the Garmin API using the DEVICE_SETTINGS_ENDPOINT with the given deviceId.
    async getDeviceSettings(deviceId: string): Promise<unknown> {
      return this.request(`${DEVICE_SETTINGS_ENDPOINT}/${deviceId}`);
    }
  • Type definition (GetDeviceSettingsDto) and Zod validation schema (getDeviceSettingsSchema) for the 'get_device_settings' tool input, requiring a deviceId string.
    export type GetDeviceSettingsDto = {
      deviceId: string;
    };
    
    export const getDeviceSettingsSchema = z.object({
      deviceId: z.string().describe('The Garmin device ID'),
    });
  • Registration of the 'get_device_settings' tool on the MCP server, with description, input schema, and handler that calls client.getDeviceSettings(deviceId).
    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) }],
        };
      },
    );
  • The API endpoint constant DEVICE_SETTINGS_ENDPOINT used by the client to construct the request URL for device settings.
    export const DEVICE_SETTINGS_ENDPOINT = '/device-service/deviceservice/device-info/settings';
Behavior3/5

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

With no annotations, the description carries the full burden. It implies a read operation ('Get') which is safe, but does not disclose error handling, permission requirements, or behavior when deviceId is invalid. Minimal but not misleading.

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 with no redundant words. Front-loaded with key information. Every word is meaningful.

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 get tool with one parameter, the description is nearly complete. It lacks details on return format or error scenarios, but given the absence of output schema and annotations, it is adequate. Could mention that it returns settings for a single device.

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 coverage is 100% and the parameter description ('The Garmin device ID') is clear. The tool description adds only the phrase 'specific Garmin device', which adds little beyond the schema. Baseline 3 is appropriate.

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

Purpose4/5

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

The description 'Get settings and configuration for a specific Garmin device' clearly states the action and resource. It distinguishes from siblings like 'get_devices' (list devices) and 'get_device_last_used' by focusing on settings/config, but does not explicitly differentiate.

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 (e.g., 'get_devices' for listing, 'get_device_solar_data' for solar details). The description does not mention prerequisites, exclusions, or preferred contexts.

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