Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

reset_state

Reset persisted app data through the simulator menu, taking an optional snapshot first and requiring confirmation; restart the app afterward to verify a clean launch.

Instructions

Reset persisted app data through the simulator menu, with a screenshot and optional APPS snapshot first. Requires confirm: true. Restart the app afterwards to observe a clean launch.

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": {
      "confirm": "<confirm>"
    },
    "name": "reset_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNoapp clears this app's data; all_apps deletes every app; simulator resets the simulator
verifyNoRead state through the debug channel after reset (default: true)
confirmYesMust be true; this is destructive
wait_msNoSettle time after invoking the menu (default: 1200)
snapshotNoSnapshot APP files before resetting (default: true for app scope)
stop_appNoKill the running app first so cached state cannot rewrite storage (default: true)
app_namesNoUppercase PRG basenames to snapshot; defaults to the last run PRG
snapshot_dirNoDirectory for the snapshot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningful work: it discloses destructiveness, that confirmation is mandatory, that app killing occurs first implicitly via the snapshot/screenshot preamble, and that a snapshot is taken before data is lost. It does not describe what happens on partial failure or what the verify step returns.

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 sentences, front-loaded with the core action and safety gate, with no filler. The middle clause ('with a screenshot and optional APPS snapshot first') is dense but earns its place as a pre-condition.

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 an 8-parameter destructive tool with no annotations and no output schema, the description covers only the default app-scoped path while the scope enum also allows wiping every app or the whole simulator — a materially different blast radius left unmentioned. The verify and wait_ms behaviors are also unaddressed beyond the schema.

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%, so the schema already documents scope, verify, wait_ms, snapshot, stop_app, app_names and snapshot_dir in detail. The description adds only the confirm requirement and the snapshot concept, which the schema already encodes, so baseline 3 is warranted.

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?

Names a specific verb and resource ('Reset persisted app data') and adds the mechanism ('through the simulator menu'), plus pre-steps (screenshot, optional APPS snapshot). It never distinguishes itself from the similarly named sibling state_reset, so an agent facing both has no basis to choose.

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 only: 'Requires confirm: true' signals a destructive gate and 'Restart the app afterwards to observe a clean launch' gives a post-condition workflow hint. There is no statement of when to prefer this over state_reset or when not to use it at all.

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