Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

terminate_simulator

Stop ConnectIQ.app and remove its isolated desktop when used; enable force for unresponsive simulators while preserving stored data.

Instructions

Terminate only ConnectIQ.app and destroy its isolated desktop if one was used. Force is for an unresponsive simulator. Does not delete stored data.

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

Input Schema

NameRequiredDescriptionDefault
forceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the whole burden. It does disclose that the isolated desktop is destroyed and stored data is preserved, which is useful, but it omits whether the call is irreversible, what happens on a no-op/error when nothing is running, and whether other running apps are affected — significant gaps for a destructive lifecycle tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short front-loaded sentences with no filler; the core action and scope lead. The misplaced "only" in "Terminate only ConnectIQ.app" is slightly ambiguous about whether it restricts the object or excludes other targets.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description should cover outcome and failure modes. It covers data preservation but not return value, error behavior when no simulator exists, or whether the desktop destruction is guaranteed to be clean.

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?

With 0% schema description coverage the description must define the only parameter, and "Force is for an unresponsive simulator" does add the key usage meaning beyond the bare boolean. It still doesn't say what force changes mechanically (e.g., skip graceful shutdown, kill process) or the difference in outcome.

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?

Uses a specific verb ("Terminate") and narrowly scoped resource ("only ConnectIQ.app and ... its isolated desktop"), which lets an agent distinguish it from the launch/run siblings. It stops short of explicitly naming the counterpart tool, but the scope is unambiguous.

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 gives conditional guidance for the single parameter ("Force is for an unresponsive simulator") and reassures about data safety, but says nothing about when to prefer this over alternatives or what state must hold before calling (e.g., whether a simulator must be running).

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