Skip to main content
Glama
Sign In
mcp-applemusic

mcp-applemusic

by suleyman416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

itunes_rate_track

Set the currently playing track's star rating (1–5) or clear it with 0.

Instructions

Set a star rating (1 to 5 stars) for the currently playing track.

Args: stars: Rating from 1 (lowest) to 5 (highest), or 0 to clear rating.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "stars": "<stars>"
    },
    "name": "itunes_rate_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
starsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the key behavior: setting a rating from 1 to 5, and clearing it with 0. It does not state error conditions or prerequisites (e.g., that a track must be playing), but for a simple rating tool this is reasonable. No contradiction with annotations 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?

The description is two concise sentences, with the parameter explanation neatly placed. Every sentence adds value with no redundancy or fluff.

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 tool with one parameter and no output schema, the description covers the essential aspects: the action, the parameter semantics, and the clearing behavior. It lacks details about error handling or the requirement that a track is playing, but these are minor for a simple rating operation. The overall completeness is adequate.

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 description adds significant meaning beyond the schema: it defines the valid integer range (1–5) and the special value 0 to clear the rating. The schema alone only says 'integer,' so this is essential information that helps the agent select the correct value.

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 the action ('Set a star rating') and the target ('the currently playing track'). It distinguishes from siblings like itunes_rate_album and itunes_favorite_track by scoping to the current track. The verb 'set' and resource 'rating' are specific.

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 description specifies 'for the currently playing track,' which clearly scopes when to use the tool. However, it does not explicitly mention alternatives or when not to use it (e.g., itunes_rate_album for albums). Thus it provides clear context but no exclusions.

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