Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

close_window

Dismiss a simulator-owned dialog using its window handle; refuses to close the main simulator window.

Instructions

Close a simulator-owned dialog by hwnd. Refuses to close the main simulator window.

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": {
      "hwnd": "<hwnd>"
    },
    "name": "close_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
hwndYesWindow handle from list_windows

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose an important guard rail (main simulator window cannot be closed), but says nothing about what happens with a stale or invalid hwnd, whether the close is graceful or forced, or what the tool returns on failure.

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 tight sentences with no filler, and the core action is front-loaded before the restriction. Slightly more structure (e.g., separating precondition from behavior) would earn a 5.

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 one-parameter, non-annotated action with no output schema, the description covers what it does and one critical boundary condition. Only error/failure behavior and the fate of the dialog's contents remain unstated, which are minor here.

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 is already documented as 'Window handle from list_windows'. The phrase 'by hwnd' in the description restates that without adding format, validity, or sourcing detail, so the baseline 3 is appropriate.

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 and resource ('Close a simulator-owned dialog by hwnd') and narrows scope to dialogs owned by the simulator, which implicitly separates it from window-management siblings like list_windows or capture_window. It does not explicitly name any alternative, so it stops short of 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?

The refusal clause ('Refuses to close the main simulator window') tells the agent one case where the tool will not apply, which is useful. However, there is no positive guidance on when to reach for this versus close_storage_editor, and no stated precondition such as obtaining the hwnd from list_windows first.

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