Skip to main content
Glama

window_mode

Read or switch the Unflick player window shape among full player, always-on-top picture-in-picture, and compact music layout; available only while the GUI is running.

Instructions

Get or set the shape of the player window the user is looking at. normal is the full player, pip is a small always-on-top video window, music is the compact audio layout with cover art and tags. Call with no arguments to read the current mode. Only works while the unflick GUI is running — the headless daemon has no window and says so.

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

Input Schema

NameRequiredDescriptionDefault
modeNoMode to switch to. Omit to read the current one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/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 mostly succeeds: it discloses that setting a mode mutates a user-visible window state, that the operation is a read when the parameter is omitted, and that calls fail with an explanatory message under the headless daemon. It does not say whether the chosen mode persists across sessions or whether switching interrupts playback, leaving some mutation behavior unstated.

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?

Three sentences, front-loaded with the core get/set purpose, then the mode glossary, then the environment constraint. Every sentence provides information an agent needs to call the tool correctly, with no restatement of the name or 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 single optional enum parameter with no output schema, this is complete: it explains both read and write behavior, defines every enum value, and flags the runtime environment requirement plus how failure is signaled. There is no output schema, and the description adequately implies the return is the current mode when called without arguments.

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% and the enum values are already enumerated in the schema, so the baseline applies. The description does add real meaning beyond the schema by explaining what 'normal', 'pip', and 'music' each look like, but the schema already documents that omitting the parameter reads the current value, so the added value is moderate rather than substantial.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb pair and resource: 'Get or set the shape of the player window.' It then disambiguates the three modes concretely (full player, small always-on-top video, compact audio layout), so an agent knows exactly what the tool acts on. No sibling in the catalog shares this window-shaping responsibility, so there is no ambiguity to resolve.

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 explicitly states the read path ('Call with no arguments to read the current mode') versus the write path (supply a mode), which is the key usage decision for a get/set hybrid. It also states an environment precondition: only works while the unflick GUI is running, and the headless daemon reports it has no window. It does not name alternative tools or say when not to use it, which keeps it from a 5.

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