Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

List devices

sdk_devices_list
Read-onlyIdempotent

List installed Connect IQ devices and filter them by name, shape, touch support, minimum API level, or a project manifest’s products to find compatible targets.

Instructions

Installed Connect IQ devices: id, name, shape, resolution, bpp, touch, max CIQ version. Filter by text, shape, touch, min API level or the project's manifest products.

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

Input Schema

NameRequiredDescriptionDefault
limitNomax devices (default 200)
queryNopart of the id or display name; case, accents, ® and spaces are ignored ("Fenix 7" finds fenix7)
shapeNoscreen shape
touchNoonly touch (true) or non-touch (false) devices
min_apiNominimum Connect IQ version, e.g. 4.2.0
in_manifestNomanifest.xml (or project dir) inside the root; keep only its products

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 openWorldHint=false, so the safety profile is covered. The description adds value by enumerating the returned fields, which matters because no output schema exists; it does not mention default page size behavior beyond the schema's limit default.

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?

Two dense sentences: first the resource and returned fields, then the filter set. No filler and the payload is front-loaded.

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 read-only listing tool with full annotation coverage and no output schema, the description supplies the return shape and filter surface. Pagination limits are left entirely to the schema, a minor gap but not a blocking one.

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 each parameter is documented inline (including query normalization semantics), so the description's filter recap adds essentially nothing beyond the schema. 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 concrete resource (installed Connect IQ devices) and enumerates the attributes returned (id, name, shape, resolution, bpp, touch, max CIQ version), so the agent knows exactly what it gets. It does not explicitly distinguish itself from the singular sibling sdk_device_get, which would be needed for a 5.

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?

It lists the available filter dimensions, which implies usage (find/filter devices rather than fetch one), but never states when to pick this over sdk_device_get or when not to filter. Usage is inferable but not spelled out.

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