Skip to main content
Glama

timeline

Schedule key and pointer events at millisecond precision in an app's background window, then send the full sequence once for timing-sensitive tasks like music, games, drags, and holds.

Instructions

Play key and pointer events on a millisecond schedule in an app's window, in the background. For input whose timing matters: music, games, drags, holds. Plan the whole sequence, then send it once. One event per line, MS VERB ARGS (MS = time from the start): MS down KEY · MS up KEY · MS tap KEY [HOLD_MS] · MS down X,Y [right] · MS up X,Y [right] · MS move X,Y · MS tap X,Y [HOLD_MS] [right]. KEY like a, shift+a, space, left. X,Y are window points. HOLD_MS defaults to 40.

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": {
      "app": "<app>",
      "events": "<events>"
    },
    "name": "timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYes
eventsYes
windowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses that input is scheduled relative to a start time, executed in the background, and dispatched as one batch rather than per-interaction. It does not cover prerequisites (does the app need to be running? focused?), failure behavior, or what is returned, which are meaningful gaps for an input-injection tool.

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?

Dense and front-loaded: purpose, use case, workflow rule, then the grammar table. The terse '·'-separated verb list is the most compact way to convey six event forms, and every clause carries information an agent needs to construct a valid events array.

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 3-parameter, annotation-free, no-output-schema tool, the description covers the format and timing model needed to produce a correct events list. It falls short on the two string parameters (app, window) and on runtime failure behavior, but the core invocation contract is present.

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 coverage is 0%, so the description must compensate. It thoroughly specifies the hardest parameter, events, including line grammar, all six verb forms, key syntax, coordinate meaning, and the HOLD_MS=40 default. However, 'app' and 'window' get no explanation at all — it never says whether window is a title, handle, or selector, or how app strings are resolved.

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: play key and pointer events on a millisecond schedule inside an app's window, in the background. The 'background' + 'plan the whole sequence, then send it once' framing implicitly separates it from a direct foreground input tool like act, but no sibling is named explicitly.

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 a clear class of use cases: 'For input whose timing matters: music, games, drags, holds', plus a workflow rule ('plan the whole sequence, then send it once'). It stops short of naming the alternative tool (e.g. act) for untimed input, so the agent must infer when-not to use this.

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

Deploy Server

Other Tools