Skip to main content
Glama
Golden Hour Selector

Golden Hour Selector

by neleus-agent

search

Find Spotify tracks by name or artist and return matching spotify: URIs, enabling you to resolve a song name to a URI before playing it on another device.

Instructions

Search Spotify for tracks by name and return the top matches with their spotify: URIs. Does NOT play — use to resolve a song name to a URI (e.g. to then play it on a Sonos room via mcp-sonos).

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": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesTrack name (and optionally artist) to search for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose that the operation is a lookup returning top matches with URIs and that it has no playback side effect. It does not say how many matches are returned, whether authentication is required, or anything about rate limits, so some behavioral detail is left implicit.

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 sentences, front-loaded with the action and result, followed by the crucial disambiguation. No filler, and every clause carries information the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter lookup tool with no output schema, the description supplies the action, the return content, and the boundary against playback. Nothing essential for correct invocation is missing.

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?

Schema coverage is 100% for the single query parameter, so the schema already documents it. The description reinforces the semantics by saying tracks are searched by name and that an artist may optionally be included, adding a small amount of meaning beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 ("Search Spotify for tracks by name") and states the return payload (top matches with spotify: URIs). It also explicitly separates itself from the playback tools by saying it does NOT play, so an agent can distinguish it from siblings like play without opening either schema.

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?

It gives a clear when-to-use case (resolve a song name to a URI, then play it on a Sonos room) and a clear when-not (this tool does not play). The only gap is that it never names the sibling play tool directly as the alternative for playback, leaving the agent to infer that from the negation.

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