Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

set_active_device

Set the active Garmin device ID so later simulator commands, button presses, touch gestures, and screenshot cropping target the correct watch model.

Instructions

Set the active Garmin device ID for subsequent simulator commands, button presses, touch gestures, and screenshot cropping.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "device_id": "<device_id>"
    },
    "name": "set_active_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_idYesTarget device ID (e.g. 'fenix847mm', 'venu3', 'fr965', 'epix2pro47mm')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does convey the key trait that this is a stateful, session-affecting selection rather than a one-shot action. It omits what happens on an invalid or unknown device ID, whether the setting persists across sessions, and whether confirmation is returned.

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?

A single sentence with no waste, front-loading the action and then the consequences. Every clause earns its place by naming the dependent operations.

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-parameter state-setting tool with no output schema and no annotations, the description is close to sufficient: it establishes the action and its downstream effect. It falls slightly short on failure modes and selection lifetime, which an agent would want before relying on it.

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 description coverage is 100% and the single parameter already documents the target device ID with concrete examples ('fenix847mm', 'venu3', 'fr965'), so the description adds nothing beyond it. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource ('Set the active Garmin device ID') and clarifies the effect scope: it governs subsequent simulator commands, button presses, touch gestures, and screenshot cropping. It never names a sibling (e.g. list_devices) to differentiate against, so it lands at clear-but-undifferentiated rather than fully distinguishing.

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

Usage Guidelines4/5

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

It gives real usage context by naming the operations that depend on the selection, which tells an agent when this must be called (before those commands). It stops short of exclusions or prerequisites, such as whether the device must already exist or whether a prior selection is required.

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