Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

Get device

sdk_device_get
Read-onlyIdempotent

Retrieve full specifications for an installed Garmin device—display, buttons, touch, memory limits, CIQ version, and languages—by device ID.

Instructions

Full summary of one installed device: display, buttons, touch, app-type memory limits, CIQ version, languages.

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": {
      "id": "<id>"
    },
    "name": "sdk_device_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesdevice id as in manifest products, e.g. fenix7

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so the description is not required to establish safety. It adds real context by disclosing what the response payload contains (the field list), which matters because there is no output schema. It does not say what happens for an unknown or non-installed id.

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?

One sentence, front-loaded with the purpose and then the returned fields. No filler, no restatement of the title.

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?

With no output schema, the description carries the burden of describing the return value and does so concretely by enumerating the summary's sections. For a single-parameter read tool that is largely sufficient; only error/not-found behavior is left unaddressed.

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 coverage is 100% and the single parameter already documents the manifest product id format (e.g. fenix7). The description reinforces that the id must refer to an installed device but adds no syntax or format detail beyond the schema, so the 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?

States a specific verb+resource (returns a summary of one installed device) and enumerates exactly what the summary covers: display, buttons, touch, memory limits, CIQ version, languages. The word "one" implicitly distinguishes it from the sibling sdk_devices_list, though that sibling is never named.

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: the agent can infer this is for looking up a single device by id versus listing devices. There is no explicit when-to-use statement, no mention of the id coming from a manifest, and no named alternative for enumerating multiple devices.

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