Skip to main content
Glama
Golden Hour Selector

Golden Hour Selector

by neleus-agent

play

Search Spotify by track name and start it on the active device or a named device such as a Sonos room, then return the current track status.

Instructions

Search Spotify for a track by name and start playing it. Plays on the active device, or on a named device (e.g. a Sonos room) when 'device' is given. 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": {
      "query": "<query>"
    },
    "name": "play"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesTrack name (and optionally artist) to search and play
deviceNoOptional device name to play on (partial match), e.g. Kitchen, Bedroom

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. It usefully discloses the default target device and that it returns the now_playing state, but it doesn't say whether starting playback interrupts the current track, what happens if the search finds nothing or matches several tracks, or whether device/auth prerequisites exist.

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?

Three tight sentences: the action and search scope come first, then device targeting, then the return value. Nothing is repeated or wasted.

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 tool this covers the essentials: what it does, where it plays by default, how device selection works, and what it returns, so no output schema is needed. The remaining gap is failure and interruption behavior, a modest omission for a simple playback action.

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, including 'partial match' for device. The description adds only the default behavior (active device when 'device' is omitted), which is a marginal gain over the schema and matches the baseline 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?

The description uses a specific verb and resource: it searches Spotify for a track by name and starts playing it, which separates it from a pure 'search' tool. It never names a sibling (search, play_mood, pause_resume), so the agent must infer the boundary itself rather than read it.

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 sentence about playing on the active device unless 'device' is given implies the main usage scenario, but the description never states when to prefer this over 'search' or 'play_mood', and it gives no exclusion or prerequisite guidance. The guidance is useful but inferred, not explicit.

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