Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

state_reset

Clears all app storage keys through the in-app debug channel and optionally verifies the resulting state, helping reset Connect IQ app data for repeatable simulator tests.

Instructions

Clear every app storage key through the in-app debug channel and optionally report the resulting state.

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

Input Schema

NameRequiredDescriptionDefault
verifyNoRead state after clearing (default: true)
timeout_msNoTimeout in milliseconds (default: 10000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that all app storage keys are wiped and that reporting is optional, but it never states that the operation is destructive/irreversible, what happens if the app or debug channel is unavailable, how timeout_ms affects failure, or what the 'resulting state' report contains.

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 sentence with front-loaded verb and scope, and zero redundant wording. Every clause contributes either what is cleared or how results are reported.

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 two-optional-parameter mutation tool with no annotations and no output schema, the definition covers purpose well but leaves the destructive/irreversibility profile and return behavior unexplained. An agent could call it correctly but would not fully understand the risk or the response.

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 both parameters are already documented, and the description only loosely ties 'optionally report the resulting state' to the verify flag. It adds a little conceptual framing but no format, default, or edge-case detail beyond the schema.

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 names a specific verb ('Clear') plus resource ('every app storage key') and the mechanism ('in-app debug channel'), which is more precise than the bare name state_reset. It does not explicitly distinguish itself from sibling 'reset_state', so an agent must infer the difference from the resource scope alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool, when not to, or which sibling (e.g., reset_state or state_seed) to prefer. The only usage signal is implicit in the word 'Clear', leaving alternative selection entirely to inference.

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