Skip to main content
Glama
Sign In
lyricmood-mcp

lyricmood-mcp

by yigitates17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Artist Tracks

get_artist_tracks

Fetches an artist's tracks ranked by Last.fm listeners and resolves them to Spotify, using Spotify search order when Last.fm data is unavailable.

Instructions

An artist's most popular tracks (by Last.fm listeners), resolved to Spotify. Falls back to Spotify search order when Last.fm has no data.

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": {
      "artist": "<artist>"
    },
    "name": "get_artist_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax tracks (1-25).
artistYesArtist name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does real work: it discloses the ranking source (Last.fm listeners), the Spotify resolution step, and the fallback ordering when Last.fm has no data — non-obvious behavior an agent could not infer from the schema. It stops short of describing what each returned track contains or any auth/failure behavior, and there is no output schema to fill that gap.

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 tight sentences with the ordering rule front-loaded and the fallback trailing as secondary information. Nothing is redundant, though it is arguably terse for a tool with no annotations or output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter lookup the description covers the important ranking and fallback semantics, but with no annotations and no output schema the agent still does not know the return shape, whether Spotify linking is required, or what happens on artist-name mismatch.

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 description coverage is 100%, so both parameters are already documented, establishing a baseline of 3. The description adds only indirect meaning — that the "artist" name is resolved against Spotify — without explaining ambiguity handling or how limit interacts with the fallback path.

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?

States a specific verb and resource: the artist's most popular tracks, with the ranking source named (Last.fm listeners) and the resolution target (Spotify). The possessive "An artist's" implicitly separates it from get_my_top_tracks and get_track_profile, though no sibling is named explicitly.

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?

Usage is implied by the resource: call it when you want an artist's top tracks. There is no explicit when-to-use versus search_track or get_track_profile, and no stated prerequisites (e.g. whether a Spotify connection is required).

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