Skip to main content
Glama

get_device_settings

Read-only

Retrieves configuration settings for a Garmin device, including time/date format, units, activity tracking, and alarms. Omit device ID to use the most recently used device.

Instructions

Get settings for a specific Garmin device

    Returns device configuration including time/date format, units,
    activity tracking settings, and alarm information.

    Args:
        device_id: Device ID (optional; defaults to the most recently used
            device when omitted; can be obtained from get_devices or
            get_device_last_used)
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_device_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds the valuable detail that the response is a configuration payload with specific sections, which matters because no output schema exists. It stops short of noting auth requirements, error behavior for an invalid device_id, or whether the settings are cached/stale.

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?

Front-loaded with the one-line purpose, then the response contents, then the single argument note. The docstring-style 'Args:' block is compact and readable, and no sentence is redundant.

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 one-optional-parameter read tool with no output schema, coverage is nearly sufficient: purpose, return contents, and the default behavior are all present. Missing only the ID format ambiguity and failure-mode behavior for an unknown device.

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?

Schema coverage is 0%, so the description must carry the load, and it does: it explains that device_id is optional, what the omission fallback is, and where valid IDs come from. The gap is the accepted ID form — the schema permits integer, string, or null, but the description does not say which representation is expected.

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?

States a specific verb and resource ('Get settings for a specific Garmin device') and enumerates the settings returned (time/date format, units, activity tracking, alarms), so the agent knows exactly what it fetches. It does not distinguish itself from nearby siblings like get_device_alarms, which overlaps with the 'alarm information' it claims to return.

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?

Explicitly states the parameter is optional and what happens when omitted ('defaults to the most recently used device'), and names the two sibling tools (get_devices, get_device_last_used) that supply a device_id. That is concrete when-to-use and prerequisite guidance rather than inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools