Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

Edit manifest products

sdk_manifest_set_products

Add or remove device product entries in a Garmin manifest.xml while keeping the rest of the file unchanged. Use it to target installed devices for Connect IQ builds.

Instructions

Add/remove iq:product entries in manifest.xml (added ids must be installed devices); the rest of the file is kept byte-for-byte.

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

Input Schema

NameRequiredDescriptionDefault
addNodevice ids to add (must be installed)
pathNomanifest.xml or project dir inside the root (default: root)
removeNodevice ids to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description adds meaningful context beyond them by promising the remainder of manifest.xml is untouched byte-for-byte, which reassures the agent about formatting preservation, and by disclosing the installed-device validation rule as a failure mode. It does not address idempotency (annotations say idempotentHint=false) or what happens on partial failure across the add list.

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 dense sentence with the mutation scope front-loaded and the file-preservation guarantee immediately after. Every clause carries information; nothing is padding.

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?

For a three-parameter mutation tool with no output schema, the description covers what is changed and what is preserved but says nothing about the return value, what occurs if some add ids fail validation (partial application vs atomic), or whether a missing manifest.xml is created. These are non-trivial gaps for a file-mutating tool, though the annotations and schema cover much of the rest.

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 all three parameters (add, remove, path) are already documented in the schema, including the 'must be installed' constraint on add. The description restates that constraint but adds no new syntax, format, or interaction detail between add and remove, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair (add/remove), the exact resource (<iq:product> entries in manifest.xml), and the scope guarantee that the rest of the file is preserved byte-for-byte. This distinguishes it clearly from the read-only sibling sdk_manifest_get without the agent needing to open either schema.

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?

Provides a concrete precondition for use: added ids must already be installed devices, which tells the agent the edit will fail otherwise. It does not name an alternative tool (e.g. how to enumerate installed devices before calling) or state when-not to use it, so guidance is clear but not complete.

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