Skip to main content
Glama
Golden Hour Selector

Golden Hour Selector

by neleus-agent

pause_resume

Pause, resume, or toggle Spotify playback on the active device, then return the current now-playing state.

Instructions

Pause, resume, or toggle Spotify playback on the active device. Returns the now_playing state.

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

Input Schema

NameRequiredDescriptionDefault
actionNoDefault: toggle

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 must carry the full behavioral burden. It usefully discloses that the action applies to the active device and that it returns the now_playing state, but it is silent on failure modes such as what happens when no active device exists or whether the call is idempotent.

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 short sentences, both front-loaded: the operation and its scope first, then the return value. No redundant or filler wording.

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 simple one-optional-parameter playback tool, the definition covers the action set, the device scope, and the return value. The only gap is omitted error/edge-case behavior when no active device is present.

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%: the single 'action' parameter has an enum of pause/resume/toggle and a documented default of toggle. The description adds no additional meaning beyond the schema, so the baseline of 3 applies.

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 states specific verbs (pause, resume, toggle) and the resource (Spotify playback), plus a scope qualifier: 'on the active device'. It does not explicitly contrast with siblings like 'play' or 'skip', so sibling differentiation is left implicit, but the purpose is unambiguous.

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 only implied by the verb list; there is no statement of when to prefer this over 'play' or 'skip', and no prerequisites such as needing an active device session. An agent can infer the intent, but nothing in the text routes it between alternatives.

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