Skip to main content
Glama

session

Tracks the last watched video and playback position, restores it after a crash or closed window, and clears the record on request.

Instructions

What the user was last watching and how far in — and, with action "restore", reopen it there. unflick writes this down every few seconds while playing, so it survives a closed window or a crash. Use it when someone asks to get back to what they were watching without naming the file. "clear" forgets it.

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

Input Schema

NameRequiredDescriptionDefault
actionNoDefaults to show, which only reports.

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 supplied, the description carries the full burden and does real work: it discloses that the state is written every few seconds while playing and survives a closed window or crash, and that 'clear' forgets it while 'restore' reopens the file. It does not say what 'show' actually returns (position format, title, or behavior when nothing is recorded), which is the main remaining disclosure gap for a mutation-capable tool.

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?

It is short, front-loaded with the core definition, and every clause carries information. The em-dash-heavy phrasing and the trailing 'clear forgets it' fragment make it slightly harder to scan than a clean clause-per-mode structure.

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 single-optional-enum tool with no output schema and no annotations, this covers the essential behavior: persistence cadence, crash resilience, and the effect of each mode. It is incomplete only on the returnside — an agent cannot tell what 'show' yields when a session exists versus when none does.

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% and the only parameter is an enum already documented as defaulting to show, but the description still adds semantics beyond the schema: it explains what each mode does behaviorally (show only reports, restore reopens the file, clear forgets). That is meaningful value over a bare enum.

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 the resource precisely ('what the user was last watching and how far in') and enumerates the three modes (show/restore/clear), so an agent understands it is a resume-point store rather than a generic player control. It stops short of 5 because it never names the adjacent tools an agent might confuse it with (bookmark_add/bookmark_goto), leaving that distinction to inference from 'without naming the file'.

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?

It gives an explicit triggering condition: use it when someone wants to get back to what they were watching without naming the file. That is a clear context cue and implicitly excludes named-file navigation. No sibling is named as the alternative and there is no explicit 'do not use when' clause, so it lands at 4.

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