Skip to main content
Glama
Golden Hour Selector

Golden Hour Selector

by neleus-agent

skip

Skips to the next or previous track on the active Spotify device and returns the now-playing state, so agents can advance playback and confirm what is playing.

Instructions

Skip to the next or previous track on the active Spotify device. Returns the now_playing state.

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": {
      "direction": "<direction>"
    },
    "name": "skip"
  }
}

Input Schema

NameRequiredDescriptionDefault
directionYesSkip direction

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/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 it does disclose the return value ('Returns the now_playing state'), which is genuinely useful. It omits edge-case behavior such as skipping past the end of a queue, wrapping at the first track, or the failure mode when no active device exists.

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 short sentences, action first and return behavior second, with zero filler. Every sentence contributes information an agent needs.

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 one-parameter, non-destructive playback control, the definition covers what it does and what it returns, which is enough to call it correctly. Only the no-active-device failure path is left unaddressed, a minor gap given the tool's simplicity.

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% and the single enum parameter is fully documented in the schema, including both allowed values. The description's 'next or previous' mirrors the enum without adding format or edge-case meaning, so the baseline 3 applies.

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 names a specific verb (skip), resource (track), and directionality (next/previous) on the active Spotify device, which cleanly separates it from siblings like play, pause_resume, and now_playing. It stops short of naming an alternative explicitly, so it is clear but not fully sibling-differentiated.

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 phrase 'on the active Spotify device' implies a prerequisite (a device must already be active), which is useful implied guidance. However, it never states when to use this versus play or pause_resume, nor what to do when no device is active (e.g., use transfer or launch_app), leaving the agent to infer.

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