Skip to main content
Glama
Sign In
lyricmood-mcp

lyricmood-mcp

by yigitates17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Now Playing

now_playing

Retrieves the Spotify track currently playing and optionally its lyrics, audio features, and tags so you can explain the song or answer “what’s playing” questions.

Instructions

The song currently playing on the user's Spotify, with its profile (lyrics, audio features, tags) so you can explain it right away. Use it when the user says "this song", "what's playing", etc.

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

Input Schema

NameRequiredDescriptionDefault
with_profileNoInclude the song's full profile (lyrics, features, tags).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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 carries the full behavioral burden. It usefully discloses that the response bundles lyrics, audio features and tags, but says nothing about read-only nature, what happens when nothing is playing or no account is connected, or response shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core capability front-loaded and the trigger examples second. The trailing 'so you can explain it right away' is mild padding but does signal intent.

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 one-optional-parameter read tool with no output schema, the description covers both what comes back and when to call it. The main remaining gap is the empty-state behavior, which matters for a 'currently playing' query.

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% for the single optional boolean, and the schema already explains that with_profile controls inclusion of lyrics, features and tags. The description restates that same content in its opening clause without adding format or cost trade-off detail.

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 names a specific resource and scope: the song currently playing on the user's Spotify, plus its bundled profile (lyrics, audio features, tags). That is enough for an agent to separate it from siblings like get_track_profile or get_lyrics, though it never explicitly states the distinction.

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?

It gives concrete invocation triggers with quoted user phrasings ('this song', 'what's playing'), which is stronger than generic context. It offers no exclusions or named alternatives for cases where the user means a song that is not currently playing.

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