Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

list_devices

Lists installed Garmin device profiles from the Connect IQ SDK Devices directory, showing display resolution, touch support, screen shape, and buttons; optionally filter by name or touchscreen-only.

Instructions

List all installed Garmin device profiles in Connect IQ SDK Devices directory with display resolutions, touch support, screen shape, and available buttons.

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": "list_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoFilter devices by ID or display name substring (e.g. 'fenix', 'forerunner', 'venu', 'edge')
touch_onlyNoOnly return touchscreen-enabled devices

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
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 usefully discloses what comes back (resolutions, touch support, screen shape, buttons) and hints at a dependency on an installed SDK directory, but says nothing about ordering, empty results, or failure when the SDK is absent, and 'List all' arguably understates the filterable behavior.

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 front-loaded sentence with no filler; the resource and location come first and the returned fields follow as a compact enumeration. Nothing here could be cut without losing information.

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 zero-required-parameter, read-only listing tool with no output schema, the description covers the essential facts: what is listed, where from, and which attributes are returned. Minor gaps around filtering and returned-result edge cases keep it short of a 5.

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%, so both the 'query' substring filter and 'touch_only' flag are already documented with examples. The description adds no parameter meaning and its 'List all' phrasing slightly points away from the filters, but the schema carries the load, so baseline 3 applies.

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 names a specific verb and resource ('List all installed Garmin device profiles') and pins down the source ('Connect IQ SDK Devices directory'), plus the fields returned. That is enough to separate it from siblings like set_active_device or launch_simulator, though it never names an alternative explicitly.

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 discovery step before set_active_device, but the description never says when to call it or when not to. There is no mention of the filtering parameters as a reason to call it, so the agent must work that out from the schema.

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