Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

snapshot_app_files

Back up specified PRG app files from the simulator APPS directory by explicit basename without stopping the app; use an idle or stopped session.

Instructions

Back up only files matching explicit PRG basenames from simulator APPS. Does not stop the app; use an idle/stopped session.

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": {
      "directory": "<directory>",
      "app_names": "<app_names>"
    },
    "name": "snapshot_app_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_namesYes
directoryYes

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, and it does disclose two real behaviors: it does not stop the app and it requires an idle/stopped session. It omits other consequential traits such as whether existing snapshots are overwritten, where the backup is written, what happens if a listed basename has no matching file, and whether the operation is read-only on the app.

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, zero filler, with the scope constraint front-loaded before the operational caveat. Nothing is redundant or padded.

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

Completeness2/5

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

For a two-parameter file-backup tool with no annotations, no output schema, and no schema descriptions, the definition is too thin. An agent still cannot tell what 'directory' means, what the call returns, or what side effects occur on the filesystem.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, so the description must compensate and largely does not. 'app_names' is only obliquely hinted at by 'explicit PRG basenames', and 'directory' is never explained at all — it is unclear whether it is the source app directory or the backup destination, which is a critical ambiguity for a file-copy tool.

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 and resource: backing up files from simulator APPS, with a scope qualifier ('only files matching explicit PRG basenames'). An agent can tell this is a backup/snapshot operation rather than a run or build. It does not name the obvious counterpart restore_app_files, and the term 'PRG basenames' and 'APPS' are unexplained jargon that leaves the exact target set partly opaque.

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

Usage Guidelines4/5

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

Gives an explicit precondition: the session must be idle/stopped because the tool does not stop the app itself, which implicitly tells the agent when not to call it. No named alternative or fallback is offered for the running-app case, so it falls short of a full when/when-not/alternatives statement.

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