Skip to main content
Glama

script_remove

Remove an installed mpv user script from the config scripts directory by specifying its filename or stem.

Instructions

Delete an installed mpv user script from the config scripts directory.

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>"
    },
    "name": "script_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesScript filename or stem to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. "Delete" plus "config scripts directory" implies permanent on-disk file removal, but the description never says whether removal is reversible, whether it requires confirmation, whether it fails when the script is absent or currently active, or whether mpv must be restarted. For an irreversible mutation tool this leaves significant gaps.

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?

A single front-loaded sentence with no filler, hedging, or redundant restatement of the tool name. Every word contributes to identifying the resource and its location.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is structurally simple (one required string parameter, no output schema), so little explanation is needed. However, as a destructive operation with zero annotations, the definition should at minimum describe failure modes and irreversibility, which it omits.

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% for the single parameter, and the schema already explains that it accepts a filename or stem. The description adds only the notion that the script must be an installed user script, not the extension/stem semantics or case sensitivity. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource ("Delete an installed mpv user script") and adds a precise location ("the config scripts directory"), which goes beyond the bare name. It does not explicitly distinguish itself from siblings like script_add, script_list, or script_toggle, so it stops short of a 5.

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?

Usage is implied rather than stated: the agent can infer this is the inverse of script_add and applies only to installed user scripts. There is no explicit when-to-use/when-not guidance, no mention of how to discover scripts first (script_list), and no note about what happens if the script is currently enabled.

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