Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

set_glance_mode

Toggle or set the simulator Glance View mode to test widget glance summaries. Optionally captures a screenshot after toggling and lets you set a wait time.

Instructions

Toggle or set the simulator Glance View mode (Settings > Glance View) for testing widget glance summaries.

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

Input Schema

NameRequiredDescriptionDefault
enabledNoTarget glance view state (true to enable, false to disable, or omitted to toggle)
wait_msNoMilliseconds to wait before capturing screenshot (default: 400)
capture_afterNoWhether to capture a screenshot after toggling (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, and it only says it toggles a view mode. It does not disclose the notable default side effect of capturing a screenshot and waiting 400ms, whether the setting persists across launches, or whether the underlying widget state is reset. It clarifies toggle-vs-set semantics in the schema, not the prose.

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?

A single front-loaded sentence with the action first and scope parenthetical after; no filler or restated boilerplate.

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 three-parameter, all-optional tool with full schema coverage and no output schema, the description is adequate. It omits preconditions and the screenshot side effect that a mutation-and-capture tool arguably should surface.

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 description coverage is 100%, so the meaning of enabled, wait_ms, and capture_after is fully documented in the schema. The description adds only the UI path context and no parameter-level detail, so the 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?

States a specific verb pair (toggle/set) and a specific resource (simulator Glance View mode), with a UI breadcrumb 'Settings > Glance View' and a stated domain ('widget glance summaries'). An agent can grasp what the tool manipulates without opening the schema, though it doesn't explicitly contrast itself with other simulator-state tools like set_active_device.

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 phrase 'for testing widget glance summaries' implies the use case, but there is no explicit when-to-use, no prerequisites (e.g., simulator must be launched), and no exclusions or alternatives named among the many sibling tools.

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