Skip to main content
Glama
Golden Hour Selector

Golden Hour Selector

by neleus-agent

launch_app

Launch the local Spotify desktop app to make it a controllable playback device, then report available devices when none are active.

Instructions

Launch the local Spotify desktop app so it becomes a controllable device, then wait briefly and report available devices. Use when no active device is available before playing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/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 real behavior: it launches a process on the local machine, waits briefly, and returns a device list. Missing are failure modes (app not installed, headless/server environments), how long 'briefly' is, and whether it is idempotent if a device already exists.

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 its effect, followed by the routing condition. There is no wasted wording and no repeated restatement of the name.

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 zero-parameter tool with no output schema, the description usefully states what comes back ('available devices') and the temporal side effect. What remains missing is error behavior when no local app can be launched, which matters because this tool depends on the agent's host environment.

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 there is nothing for the description to clarify and the baseline applies. Nothing in the description misdescribes the (empty) input contract.

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 target ('Launch the local Spotify desktop app') and states the resulting state change ('so it becomes a controllable device'), plus the follow-up action ('report available devices'). An agent can tell this apart from list_devices or transfer without opening any 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?

The trigger condition is explicit: 'Use when no active device is available before playing.' That gives a clear when-to-use rule tied to the play flow. It does not name sibling tools as alternatives (e.g. list_devices to check first) or state when not to call it, so it stops short of full routing guidance.

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