Skip to main content
Glama

get_primary_training_device

Read-only

Retrieve the Garmin device designated as primary for training metrics and list other wearables on the account, so you can confirm which device supplies training data.

Instructions

Get information about the primary training device

Returns details about the device designated as primary for training metrics, along with other wearable devices on the account.

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_primary_training_device"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the response is not limited to the primary device but also enumerates other wearables on the account, which shapes how the agent should read the result.

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?

Two short sentences, front-loaded with the core action, with no filler or tangential detail. There is mild redundancy between "Get information about the primary training device" and the second sentence's restatement of "device designated as primary," but it is not costly.

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?

With no parameters, no output schema, and only read-only annotations, the description carries the burden of explaining what comes back. It states at a high level that device details and other wearables are returned, but does not indicate what kinds of details or how the primary device is identified in the response.

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?

This tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly presents it as a no-argument lookup rather than suggesting any filtering options exist.

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 uses a specific verb and resource ("Get information about the primary training device") and clarifies the scope by adding that other wearable devices on the account are returned too. It does not distinguish itself from nearby siblings such as get_device_settings or get_device_last_used, so the agent gets a clear purpose but no explicit differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the tool to call when it needs to know which device drives training metrics. There is no explicit when-to-use statement, no mention of prerequisites, and no named alternative for the closely related device tools.

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