Retrieve the current Apple Music track and player state, including volume, shuffle, and repeat settings.
What's playing right now, plus player state, volume, shuffle and repeat.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It usefully enumerates the returned state (player state, volume, shuffle, repeat), which is valuable given there is no output schema, but it never states that the call is read-only with no side effects or what happens when nothing is playing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence that names the primary payload first and appends the secondary state fields. No filler, no restating of the tool name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no parameters and no output schema, the description's main obligation is to say what comes back, and it does list the returned fields. It stops short of covering the empty/idle state or confirming read-only behavior, which keeps it from a 5.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 disambiguate. The baseline of 4 applies; the sentence is not misleading about inputs.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific query and its payload: 'What's playing right now, plus player state, volume, shuffle and repeat.' That distinguishes it from the control-oriented siblings (playback, set_player_options) without naming any of them explicitly, so it lands at 4 rather than 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied rather than stated: the phrase 'right now' signals a read of current state, and the sibling 'set_player_options' implies this is not the tool for changing volume/shuffle/repeat. There is no explicit when-to-use, when-not-to-use, or named alternative, so it sits at minimum viable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.