Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

capture_window

Capture a simulator-owned dialog or window by hwnd as a PNG image, with an optional save path for inspection or debugging.

Instructions

Capture a simulator-owned dialog or window by hwnd. Returns the PNG image and optional saved path.

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

Input Schema

NameRequiredDescriptionDefault
hwndYesWindow handle from list_windows
save_pathNoOptional file path to save the PNG

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 exist, so the description carries the full burden. It does disclose the output shape (PNG plus an optional saved path), which is valuable, but says nothing about permissions, whether the window is raised/focused, failure modes for invalid or stale hwnds, or size limits.

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 short sentences with zero filler: the action and target come first, followed by the return value. Nothing repeats the name or wastes the agent's attention.

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 two-parameter capture tool with a fully described schema and no output schema, the description covers the action, target, and return value adequately. Only edge-case behavior (invalid hwnd, capture failures) is left implicit.

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 both parameters are already documented, including that hwnd comes from list_windows and save_path is optional. The description adds no format or constraint detail beyond that, so the schema does the heavy lifting and 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 gives a specific verb+resource pair ("Capture a simulator-owned dialog or window") and names the selector (hwnd), so an agent knows exactly what is being produced. It does not explicitly contrast with siblings like get_screenshot or diff_screenshot, leaving the boundary to inference.

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 only implied: "by hwnd" and "simulator-owned" suggest this is for targeting a specific window rather than a whole-screen capture, and the hwnd must come from list_windows per the schema. There is no explicit when-to-use or when-to-prefer-get_screenshot guidance.

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