Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

list_windows

Lists top-level Garmin simulator windows, including storage, login, time, and phone-message dialogs, while filtering IME and hidden wx windows unless include_hidden is true.

Instructions

List top-level simulator windows, including storage, login, time and phone-message dialogs. IME and hidden wx windows are filtered unless include_hidden is true.

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

Input Schema

NameRequiredDescriptionDefault
include_hiddenNoInclude IME, tooltip and hidden wx windows (default: false)

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?

No annotations, so the description carries the burden. It does disclose an important behavioral trait beyond the flag name: IME and hidden wx windows are filtered by default, and only top-level windows are returned. It omits ordering, return shape, and whether an unstarted session errors.

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?

Two compact sentences, both front-loaded with the core purpose first and the filtering caveat second. No redundant or filler wording.

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 simple one-optional-param read tool this is nearly sufficient, but with no annotations and no output schema the agent gets no safety profile, no indication of the result structure (window handles? titles?), and no session prerequisite.

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 include_hidden description already lists IME, tooltip and hidden wx windows. The description restates the default-filtering behavior rather than adding new parameter detail, so 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?

Specific verb (List) plus resource (top-level simulator windows), and it enumerates the window kinds returned (storage, login, time, phone-message dialogs). This clearly distinguishes it from siblings like inspect_ui, capture_window, or list_devices.

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 implied — you call this to enumerate open windows before acting on one — but the description never states when to prefer it over alternatives such as inspect_ui or how it relates to session_start/launch_simulator. No explicit when-not guidance.

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