Skip to main content
Glama
Golden Hour Selector

Golden Hour Selector

by neleus-agent

play_mood

Play music matching a chosen mood, such as focus or chill, on the active device or a named device; unknown moods fall back to search.

Instructions

Play music matching a mood (e.g. focus, chill, energetic, happy). Plays on the active device, or on a named device (e.g. a Sonos room) when 'device' is given. Falls back to search on an unknown mood.

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": {
      "mood": "<mood>"
    },
    "name": "play_mood"
  }
}

Input Schema

NameRequiredDescriptionDefault
moodYesMood word, e.g. focus, chill, energetic, party, sleep
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.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it discloses two real traits — playback targets the active device unless 'device' is supplied, and unknown moods degrade to a search rather than erroring. It does not say whether current playback is interrupted, what happens if the named device is offline, or what the call reports back.

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 with the core action front-loaded, followed by device targeting and then the fallback edge case. No filler, and every clause carries operational information.

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?

For a simple two-parameter playback tool the definition covers the main paths, but with no annotations and no output schema it leaves the agent guessing about return value, interruption of current playback, and failure modes for an unreachable named device.

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 the schema already documents both parameters including mood examples and the device partial-match rule. The description adds only a little beyond that: the Sonos-room framing of 'device' and the notion of an 'active device' default. Baseline 3 is appropriate.

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 and resource — play music matching a mood — and enumerates example moods, so an agent can immediately tell this apart from generic siblings like 'play' or 'search'. It stops short of explicitly contrasting itself with those siblings, which keeps it at 4.

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: mood-based playback is the entry condition, and the definition helpfully notes that an unknown mood falls back to search, which tells the agent this call is safe with loose input. There is no explicit when-not guidance, such as pointing to 'play' for specific tracks or 'search' for known titles.

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