Skip to main content
Glama

Move or reset the device clock

emu_clock

Fast-forward the Android emulator clock to fire long-delay local notifications now, then reset it to host time with automatic time enabled.

Instructions

action "forward" turns automatic time off and moves the device clock minutes ahead, so long-delay local notifications fire now (needs this session's lease: NO_LEASE means emu_start first). action "reset" puts the clock back to host time with automatic time on; it works without a lease and is refused only while another session holds the emulator (BUSY: wait or ask the person). After a forward always call reset, also when the check failed.

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": {
      "action": "<action>"
    },
    "name": "emu_clock"
  }
}

Input Schema

NameRequiredDescriptionDefault
avdNoAVD name (default "unity-test", or the EMU_AVD environment variable of the server).
actionYes"forward" (needs minutes) or "reset".
minutesNoforward: minutes to move ahead (for Unity notifications: past fire time + 1 h).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (which only declare non-readOnly, non-idempotent, non-destructive), the description discloses side effects not visible elsewhere: automatic time gets turned off by forward, restored by reset, and reset is refused while another session holds the emulator. Lease dependency and error code semantics (NO_LEASE, BUSY) are rare, high-value behavioral detail.

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?

One compact paragraph, front-loaded with the primary action, then prerequisites, then the mandatory follow-up. Every clause carries operational information; there is no filler.

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

Completeness5/5

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

For a three-parameter state-changing tool with no output schema, the description supplies the lease requirement, refusal conditions, and the required cleanup call. Nothing an agent needs to invoke it safely and in the right order is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it ties "forward" to a required minutes value and explains the value's intent (make notifications fire now, e.g. past fire time plus an hour). The reset-without-lease case also clarifies that minutes/action combinations behave differently.

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 both concrete operations: "action \"forward\" turns automatic time off and moves the device clock minutes ahead" and "action \"reset\" puts the clock back to host time." That is a specific verb+resource pair an agent can act on. It does not explicitly contrast itself with siblings like emu_check_notification, but it does name emu_start as the prerequisite when a lease is missing.

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

Usage Guidelines5/5

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

Usage conditions are explicit and actionable: use "forward" when long-delay local notifications must fire now, use "reset" to restore host time. Prerequisites ("needs this session's lease: NO_LEASE means emu_start first"), failure handling ("BUSY: wait or ask the person"), and a mandatory follow-up ("After a forward always call reset, also when the check failed") are all stated.

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