Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

set_time

Shift the simulator app clock through the debug channel using an ISO timestamp or seconds offset, and reset it to zero. Only DebugClock code paths follow the change.

Instructions

Shift the app's clock through the debug channel. Use an ISO timestamp or an offset in seconds. Only code paths using DebugClock follow the offset.

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

Input Schema

NameRequiredDescriptionDefault
isoNoTarget ISO timestamp to move the app clock to
clearNoReset the offset to zero
timeout_msNoTimeout in milliseconds (default: 10000)
offset_secondsNoSeconds to add to the app clock

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden and does disclose one high-value caveat: only code paths using DebugClock follow the offset. However, it says nothing about whether the shift persists across restarts, how to revert (the `clear` path is never mentioned in prose), what happens on invalid or conflicting inputs, or whether elevated permissions are required.

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 action and resource, with no filler. The final caveat sentence is the most useful content and earns its place; nothing needs trimming.

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 4-parameter mutation-style debug tool with no annotations and no output schema, the description covers the core mechanism and its key limitation but leaves an agent unsure about reversibility, persistence, precedence between `iso` and `offset_seconds`, and timeout behavior. It is adequate rather than complete.

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 four parameters are already documented in structured form, establishing a baseline of 3. The description restates the two primary mechanisms (ISO timestamp, offset in seconds) but adds no new meaning and never mentions `clear` or `timeout_ms` or how they interact with the named mechanisms.

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 and resource — shifting the app's clock — and scopes it to the debug channel, which separates it from sibling tools like set_active_device or reset_state. It stops short of naming any alternative tool, but the resource is unambiguous.

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 explicit when-to-use or when-not-to-use guidance, no stated prerequisites (debug build, connected app, etc.), and no mention of alternatives such as reset_state. The only usage-adjacent content is 'Use an ISO timestamp or an offset in seconds,' which is parameter choice, not invocation guidance.

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