Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

state_seed

Writes app storage keys and debug property overrides through the in-app debug channel, optionally reads them back for verification, and deletes keys when null is supplied.

Instructions

Write storage keys through the in-app debug channel, then optionally read them back to verify. Use null to delete a key.

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_seed"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesNoStorage values to write: scalar, string array, or a flat object. premium expects { active: boolean, code: string }; deck_list expects an array of ids.
verifyNoRead back and compare after writing (default: true)
prg_pathNoPRG to restart after the snapshot; defaults to the last run PRG
snapshotNoSnapshot app storage before writing premium, license or deck keys (default: true)
app_namesNoUppercase PRG basenames to snapshot; defaults to the last run PRG
device_idNoDevice used when restarting after the snapshot; defaults to the last run device
propertiesNoDebug property overrides to store as debug_prop_<key>. Supported keys: daily_goal, reveal_behavior, auto_advance, card_order, premium_enabled, deck_data, deck_2, deck_3, deck_4.
timeout_msNoPer-command timeout in milliseconds (default: 10000)
snapshot_dirNoDirectory for the snapshot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose meaningful behavior: writes go through the in-app debug channel, values can be read back, and a snapshot/PRG restart may occur. However, it does not state what the snapshot or restart actually does to the running app, whether writes are reversible, or what happens on failure.

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?

Two short sentences, front-loaded with the primary action and followed by the deletion rule. No filler, though the second sentence is a fragment that could be folded in more cleanly.

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 nine-parameter mutation tool with no annotations and no output schema, the description covers the core write/verify/delete flow but leaves the snapshot and PRG-restart side effects largely unexplained. An agent would need to infer the risk profile of restarting an app from the parameter names alone.

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 schema already documents all nine parameters in detail. The description adds only the null-deletion convention, which is genuinely beyond the schema, but nothing else about parameter interaction or precedence.

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 states a specific verb and resource ('Write storage keys through the in-app debug channel') plus a secondary behavior (read back to verify) and a deletion mode. It is clear what the tool does, though it does not explicitly name a sibling like state_read or state_reset to differentiate itself.

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?

It gives one concrete usage rule ('Use null to delete a key') and implies verification is optional, but it never says when to prefer this over state_read or state_reset, nor when snapshotting should be disabled. Usage is implied rather than spelled out.

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