Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

schedule_wind_down

Gradually lower Spotify volume over a set duration in timed steps, then pause playback; preview with dry_run before changing or cancelling an active timer.

Instructions

Preview or start a volume wind-down: absolute-minute volume steps, then pause. Set dry_run to preview without replacing or cancelling an active timer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoPreview only: describe what would change without performing it. Default false — pass true to preview.
minutesYesTotal ramp duration in minutes (1–180)
device_idNoTarget device id; defaults to the active device
floor_volumeNoVolume floor the ramp never goes below (default 10)
step_minutesNoMinutes between volume steps (default 5)
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.1
    • addedInput schema / properties / dry_run / default
      Added value: +false
    • changedInput schema / properties / dry_run / description
      Previous value: -"Preview only: validate inputs and describe exactly what would change without performing it"New value: +"Preview only: describe what would change without performing it. Default false — pass true to preview."
  2. Changed3 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Preview only: validate inputs and describe exactly what would change without performing it",
+  "type": "boolean"
+}
  3. Addedv1.26.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations supply only destructiveHint=false, so the description carries most of the burden and does so: it discloses that a non-preview run 'replac[es] or cancell[s] an active timer' and that the ramp terminates by pausing playback. These are consequential side effects an agent couldn't infer from the schema. It doesn't say whether the wind-down persists across sessions or what happens if minutes exceeds the remaining playback time.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the primary action and the ramp mechanism front-loaded, then the dry_run caveat. Nothing is redundant with the schema text. Slightly denser than needed but every clause earns its place.

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 6-parameter mutation tool with no output schema and near-empty annotations, the description covers the essentials: what it changes, how to preview safely, and the effect on an active timer. Missing only edge-case behavior (persistence, interaction with cancel_wind_down), which keeps it from 5.

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% (every parameter is documented, including defaults and ranges), so the baseline is 3. The phrase 'absolute-minute volume steps' adds a small interpretive cue about how minutes/step_minutes are measured, but no syntax or constraint detail beyond what the schema already states.

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 ('Preview or start a volume wind-down') plus the mechanism ('absolute-minute volume steps, then pause'), so an agent knows exactly what the tool does. It stops short of naming its siblings (wind_down_status, cancel_wind_down), so differentiation is implied rather than explicit.

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?

The second sentence gives real conditional guidance: pass dry_run=true to preview, and warns that a real run replaces or cancels an active timer. That condition — interaction with an already-active timer — is the main selection risk, and it's stated. It doesn't explicitly route to cancel_wind_down or wind_down_status, so it's not a full 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