Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

act_on_ui

Interact with a freshly inspected Garmin Simulator UI element by setting its value, selecting or focusing it, or triggering AXPress and increment/decrement actions; include hwnd for dialog windows.

Instructions

Act on a freshly inspected native simulator element. set writes AXValue; AXPress activates controls. Pass hwnd for dialogs.

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": {
      "path": "<path>",
      "action": "<action>"
    },
    "name": "act_on_ui"
  }
}

Input Schema

NameRequiredDescriptionDefault
hwndNoWindow handle from list_windows; omit for the main simulator window
pathYes
valueNo
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 disclosure burden. It does add real behavioral context by explaining that set writes AXValue and AXPress activates controls, but it is silent on the other five actions, on whether the call is blocking or waits for the UI to settle, and on failure behavior when the path is stale.

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 constraint and the hwnd exception come first. It is slightly telegraphic ("AXValue" is used without explanation), but nothing is redundant.

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 four-parameter mutation tool with no annotations, no output schema, and thin schema coverage, the definition covers the workflow and two action semantics but leaves the required path input, the remaining enum actions, and any return/error behavior undocumented. It is minimally sufficient to attempt a call, not to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% (hwnd is the sole documented parameter), so the description must compensate. It clarifies hwnd's purpose and gives semantics for set/value and AXPress, but the required "path" parameter — an array of integers — is never explained in either the schema or the description, leaving the most important input undefined.

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?

"Act on a freshly inspected native simulator element" names the resource (an accessibility element from a prior inspection) and the class of operation (acting, not inspecting), which distinguishes it from inspect_ui. The verb "act" is generic on its own, but the following sentences specify that it mutates state via AXValue/AXPress, so an agent can tell what it does.

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?

"Freshly inspected" implies the prerequisite workflow (inspect_ui first) and "Pass hwnd for dialogs" gives a conditional usage rule. There is no guidance on when to prefer this over sibling interaction tools such as press_button, press_button_sequence, or send_key, and no statement of when not to use it.

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