Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

state_read

Reads an app's storage and property state through the in-app debug channel to inspect current values; scalar summaries are returned and arrays report size.

Instructions

Read the app's storage and property state through the in-app debug channel. Values are scalar summaries; arrays report size.

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

Input Schema

NameRequiredDescriptionDefault
keysNoOnly return these storage keys (property names are matched with or without the prop: prefix)
timeout_msNoTimeout in milliseconds (default: 10000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden itself. It does add meaningful return-shape information (scalar summaries, arrays report size) and signals the debug-channel dependency, but says nothing about behavior on timeout, when the channel is absent, or how errors surface.

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?

Two short sentences, front-loaded with the action and resource, with the return-shape caveat immediately after. No filler text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-optional-parameter read tool with no output schema, the description covers what is returned at a coarse level (scalars vs array sizes) and the channel used. The remaining gap is failure behavior, which matters somewhat given the debug-channel dependency.

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 keys and timeout_ms are already documented in the schema. The description adds no filter syntax, prefix handling, or timeout semantics beyond that, 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 (read) and specific resources (storage and property state), plus the transport channel (in-app debug channel). It is distinguishable from mutating siblings like state_seed or state_reset, though it never names an alternative to route between.

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 only implied: the read is scoped to the in-app debug channel, which suggests the app must be running with debugging available. There is no explicit when-to-use, when-not-to-use, or comparison against sibling state tools (state_seed, state_reset, reset_state).

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