Skip to main content
Glama
Sign In
mcp-applemusic

mcp-applemusic

by suleyman416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

itunes_list_devices

List all available AirPlay audio output devices and check which one is currently selected for playback.

Instructions

List all available AirPlay audio output devices and their selection 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": "itunes_list_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses a read-only list behavior and the fact that selection state is included. However, it doesn't disclose the response format, behavior when no AirPlay devices are available, or whether discovery can fail—moderately useful but incomplete.

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?

One 12-word sentence that front-loads the verb, scopes the operation ('all available'), and includes the key return detail ('selection state'). Zero filler words or redundant phrasing.

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 and no annotations, the description fully covers the essential scope. It could add a pointer to itunes_set_device as the companion mutation tool or mention the output shape, but is otherwise essentially complete for a simple listing operation.

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?

Tool has zero parameters; the rubric prescribes a baseline of 4. The description adds minor but real value by clarifying that 'devices' specifically means AirPlay audio output devices, not all audio devices.

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?

Uses a specific verb ('List') with a resource ('AirPlay audio output devices') and reveals what's returned ('selection state'). Clearly distinguishable from the 60+ siblings, including the related, complementary itunes_set_device.

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?

The purpose implies when to use (to enumerate output devices and check the current selection), but the description does not explicitly name alternatives or exclusions such as 'use itunes_set_device to change the active device.' Adequate context, no edge-case guidance.

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

Deploy Server

Other Tools