Skip to main content
Glama

stop_video

Stop the currently playing video and close the mpv player window to end video playback sessions.

Instructions

Stop the currently playing video and close the mpv window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'stop_video' tool which stops playback and cleans up the mpv instance.
    async () => {
      if (!mpv.isPlaying()) return textResult('No video is currently playing.');
      mpv.cleanup();
      return textResult('Video stopped.');
    }
  • src/index.ts:70-79 (registration)
    Registration of the 'stop_video' tool within the MCP server instance.
    server.tool(
      'stop_video',
      'Stop the currently playing video and close the mpv window.',
      {},
      async () => {
        if (!mpv.isPlaying()) return textResult('No video is currently playing.');
        mpv.cleanup();
        return textResult('Video stopped.');
      }
    );
Behavior3/5

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

With no annotations provided, the description carries the full burden. It successfully discloses the window-closing side effect, but omits what happens when called with no active video (error vs silent success), return value details, and idempotency characteristics.

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?

Nine words, single sentence, zero redundancy. The information is perfectly front-loaded with the action first, followed by the scope and side effect.

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?

Adequate for a simple parameterless media control. Describes the primary action and side effect clearly. Minor gap regarding edge case behavior (no active video), but acceptable given the tool's limited complexity and lack of output schema.

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?

Baseline score for zero-parameter tools. The description appropriately requires no parameter explanation, and the schema coverage is trivially 100%.

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?

Excellent specificity with concrete verb 'Stop', resource 'currently playing video', and clear side effect 'close the mpv window'. The mention of closing the window effectively distinguishes this from sibling 'pause_video'.

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?

Provides clear contextual distinction from pause_video via 'close the mpv window', implying this is for terminating the session rather than temporary suspension. Lacks explicit 'use when / use X instead' phrasing that would earn a 5.

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/ronantakizawa/social-video-mcp'

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