Skip to main content
Glama
Golden Hour Selector

Golden Hour Selector

by neleus-agent

transfer

Move Spotify playback to a named Connect device by partial name match and optionally start playback; returns now_playing.

Instructions

Move playback to a Spotify Connect device by name (case-insensitive partial match, e.g. a Sonos room like 'kitchen'). Returns now_playing.

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": {
      "device": "<device>"
    },
    "name": "transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
playNoStart playing on the target device (default true)
deviceYesDevice name to transfer playback to (partial match), e.g. Kitchen, Bedroom

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully adds case-insensitive partial matching and states the return value (now_playing), but omits key behavior for a fuzzy-match transfer: what happens on ambiguous matches, on no match, or whether auth/an active session is required.

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 tightly written sentences with the operation, matching rule, example, and return value front-loaded. No filler or redundant restatement.

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 with full schema coverage and no output schema, stating that it returns now_playing is sufficient on the return side. The remaining gap is edge-case behavior for partial-name resolution (multiple or zero matches), which matters for this tool but is a bounded omission.

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 the play default. The description adds only the case-insensitivity detail for device, which the schema's 'partial match' phrasing does not cover; a marginal but real addition, hence baseline 3.

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?

States a specific verb and resource: 'Move playback to a Spotify Connect device by name.' This distinguishes a transfer operation from siblings like play, pause_resume, list_devices, and launch_app without requiring the schema to be opened.

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 by 'move playback to a device by name', but the description never says when to choose this over play or launch_app, nor does it point to list_devices as the way to discover valid device names. An agent must infer the workflow.

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