Skip to main content
Glama
Sign In
mcp-applemusic

mcp-applemusic

by suleyman416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

itunes_get_track_audio_info

Retrieve technical audio details like bitrate, sample rate, BPM, cloud status, format, and volume adjustment for a specified song or the currently playing track.

Instructions

Get technical audio quality information (bitrate, sample rate, BPM, cloud status, format, volume adjustment).

Args: song: Optional track title. If empty, inspects currently playing track.

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_get_track_audio_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
songNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A4.1/5.0
Behavior4/5

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

Without annotations, the description implies a read-only operation via 'Get', but does not explicitly state side effects or permissions. It is sufficiently clear for a getter.

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?

The description is concise, using two sentences to convey the purpose and parameter behavior without unnecessary details.

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?

The description lists the returned attributes, providing enough context for expected output, though no detailed output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'song' is well explained: optional track title, and behavior when empty (inspecting current track) is specified.

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 clearly states it retrieves technical audio quality information and lists specific attributes (bitrate, sample rate, BPM, etc.), distinguishing it from other getters.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like get_stream_info or get_track_metadata; only the purpose is stated.

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