Skip to main content
Glama
Sign In
lyricmood-mcp

lyricmood-mcp

by yigitates17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Track Profile

get_track_profile

Retrieve a song's lyrics with stats, audio features, and Last.fm mood/genre tags in one call to explain what it is about and why listeners may like it. Reports missing sources.

Instructions

Everything about one song in a single call: lyrics (possibly truncated) with simple stats (repeated lines usually mark the chorus), audio features from ReccoBeats (valence = musical positivity, energy, danceability, acousticness, tempo, key), and Last.fm mood/genre tags. Any source can be missing; missing says which and why. Use this to explain what a song is about or why someone might like it.

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": {
      "track": "<track>"
    },
    "name": "get_track_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackYesThe song: a Spotify track ID/URL/URI (best: use `id` from search_track) or free text like "Carnival of Rust Poets of the Fall".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does substantial work: it warns that lyrics may be truncated, that any source can be absent, and that a `missing` field reports which source failed and why. Naming the upstream providers (ReccoBeats, Last.fm) hints at external dependency and partial-failure modes without stating latency or rate limits.

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?

Front-loaded with the core promise, then the payload breakdown, then the call-to-action. Inline glosses such as "valence = musical positivity" and "repeated lines usually mark the chorus" earn their space by making returned fields interpretable, though the parenthetical list is slightly dense.

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?

No output schema exists, and the description compensates by naming the return categories and the `missing` diagnostic, which is what an agent needs to interpret partial results. It does not discuss free-text disambiguation or response size for long lyrics, minor gaps for a one-parameter read tool.

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% and the single `track` parameter is already documented with accepted forms and a best-practice pointer to `id` from search_track. The description adds no format or resolution detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource — fetching a complete profile of one song — and enumerates exactly what it returns: lyrics with repeat stats, ReccoBeats audio features, and Last.fm mood/genre tags. The phrase "Everything about one song in a single call" distinguishes it cleanly from narrower siblings like get_lyrics or search_track.

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?

"Use this to explain what a song is about or why someone might like it" gives a clear task-based context for selection. It stops short of explicitly routing the agent to alternatives (e.g., use get_lyrics when only lyrics are needed, or search_track to resolve a free-text query first), so the when-not guidance is only implied by the "single call" framing.

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