Skip to main content
Glama
Golden Hour Selector

Golden Hour Selector

by neleus-agent

now_playing

Retrieve the current Spotify playback state, including track, artist, album, device, progress, and volume, to inspect what is playing and inform playback control.

Instructions

Get the current Spotify playback state: track, artist, album, device, progress, and volume.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "now_playing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the full behavioral burden. It does disclose that this is a passive read of state and lists the fields returned, which is the core behavioral fact. However, it never addresses the critical edge case of nothing currently playing or no active device (error vs empty result), nor any auth or polling/rate-limit considerations.

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 sentence, front-loaded with the verb and resource, with the field list appended as a compact enumeration. No filler, no redundancy.

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?

There is no output schema, so enumerating the returned fields in the description is genuinely necessary and it does so. For a zero-parameter read tool this is nearly sufficient; the only meaningful omission is the empty/no-active-playback behavior, which an agent would need before deciding how to present results.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter semantics to clarify and the description correctly introduces none. The enumerated fields are return data, not inputs, so they do not create confusion here.

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 ('Get') and resource ('current Spotify playback state') and enumerates the returned fields (track, artist, album, device, progress, volume). This clearly separates it from control-oriented siblings like play, pause_resume, and skip, though it does not name those siblings explicitly. Nothing about the purpose is ambiguous.

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 only implied: an agent can infer this is the read-side counterpart to playback controls, but the description never says when to call it versus siblings such as volume, list_devices, or play. No prerequisites or exclusions are stated.

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