get_devicesRetrieve all Garmin devices linked to your account, with ID, model, serial, and firmware version. Identifies available devices when configuring individual device settings.
List the Garmin devices registered on the account with their id, model, serial and firmware version. Use get_device_settings for the configuration of a single device.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v4.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the output fields and the scope (registered on the account). Annotations already declare readOnly and openWorld, so no contradiction. It does not mention error handling, but that is not critical for a read-only list operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences with no redundant words. It clearly separates the main function from the alternative, maintaining a logical structure.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of an output schema, the description provides the key returned fields and clarifies the tool's scope. It also offers a pointer to a related tool, making it self-sufficient for a simple list operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has no parameters, and the schema is empty with 100% coverage. The description correctly implies no inputs are needed, so there is nothing to explain.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (list) and the resource (Garmin devices) and specifies the output fields (id, model, serial, firmware version). It distinguishes from sibling tools like get_device_settings by explicitly mentioning that tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides a specific alternative (get_device_settings for configuration) indicating when not to use this tool. However, it does not mention other related tools (e.g., get_device_last_used) but the single pointer is sufficient for a listing tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.