Skip to main content
Glama

script_toggle

Enable or disable an installed mpv user script by filename or stem. Enabling loads it immediately; disabling applies on the next launch.

Instructions

Enable or disable an installed mpv user script by filename (e.g. "autocrop.lua") or stem ("autocrop"). Enabling loads the script immediately; disabling takes effect on the next launch.

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": {
      "name": "<name>",
      "enabled": "<enabled>"
    },
    "name": "script_toggle"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesScript filename or stem
enabledYesTrue to enable, false to disable

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and delivers the single most important non-obvious trait: enabling takes effect immediately while disabling only applies on next launch. It does not cover failure behavior (unknown script name, redundant enable) or any auth/permission expectations, which keeps it short of a 5.

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?

Two sentences, front-loaded with the action and the identifier contract, followed by the timing behavior. Every clause carries information an agent would otherwise have to guess.

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 two-parameter, non-destructive toggle with no output schema and no annotations, the description covers purpose, identifier format, and load timing — enough to call it correctly. Only error/edge-case behavior is left implicit.

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 100%, so both parameters are already documented, and the description largely restates them. It does add a concrete accepted form ("autocrop.lua" or "autocrop") that clarifies identifier resolution, but that is marginal over the schema baseline of 3.

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 pair (enable/disable) and resource (installed mpv user script), with the accepted identifier forms spelled out. This implicitly separates it from script_add/script_remove/script_list by scoping to already-installed scripts, though 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 Guidelines3/5

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

The description makes the enable-vs-disable choice obvious via the boolean, and the example indicates how to identify the target script. However, it never states when to reach for this versus script_add (install) or script_remove (uninstall), nor what to do if the script isn't installed — usage is implied rather than guided.

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