Skip to main content
Glama
guodaxia9527

mcp-mpv-player

by guodaxia9527
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

player_pause

Toggle between pausing and resuming media playback in mpv player.

Instructions

Toggle pause / resume playback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.js:531-536 (handler)
    Handler for 'player_pause' tool. Calls 'mpv cycle pause' to toggle pause/resume, then returns the current pause state.
    case "player_pause": {
  await ensureMpv();
  await mpv("cycle", ["pause"]);
  const paused = await getProperty("pause");
  return ok(paused ? "Paused" : "Resumed");
}
  • index.js:342-346 (schema)
    Schema definition for 'player_pause' tool. No input parameters required, description: 'Toggle pause / resume playback.'
    {
  name: "player_pause",
  description: "Toggle pause / resume playback.",
  inputSchema: { type: "object", properties: {} },
},
  • index.js:342-346 (registration)
    Registration of the 'player_pause' tool in the tools array passed to the MCP server.
    {
  name: "player_pause",
  description: "Toggle pause / resume playback.",
  inputSchema: { type: "object", properties: {} },
},

Tool Definition Quality

A3.8/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as return status, error conditions (e.g., if already paused), or side effects. The bare description leaves ambiguity.

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?

The description is a single, short sentence that conveys the essential purpose without waste.

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?

Given the tool has no parameters or output schema, the description is mostly complete. However, it could benefit from mentioning the toggle behavior or state dependencies.

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?

There are no parameters, and schema coverage is 100% by default. The description adds no parameter details, but none are needed.

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 'Toggle pause / resume playback' uses a specific verb 'Toggle' and clearly identifies the resource (pause/resume playback). It distinguishes this tool from siblings like player_play or player_stop.

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

Usage Guidelines3/5

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

The description implies usage for pausing or resuming playback but does not provide explicit when-to-use or when-not-to-use guidance. No alternatives or prerequisites are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/guodaxia9527/mcp-mpv-player'

If you have feedback or need assistance with the MCP directory API, please join our Discord server