Skip to main content
Glama
lastfm-taste-mcp

lastfm-taste-mcp

by nurasik14

track_get_similar

Read-only

Find tracks similar to a given artist and track for "more like this" discovery, returning ranked matches with 0-1 similarity scores.

Instructions

Tracks similar to one track (good for "more like this"), with a 0-1 similarity score.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results to return
trackYesTrack title, e.g. 'Weird Fishes'
artistYesArtist name, e.g. 'Radiohead'

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?

readOnlyHint=true already tells the agent this is a safe read. The description adds one piece of behavior beyond the annotations: results carry a 0-1 similarity score, which matters because no output schema exists. It does not mention ordering, whether the seed track is excluded, or how the limit interacts with ranking.

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?

A single front-loaded sentence that delivers purpose, a use-case hint, and the return characteristic with no filler. Nothing could be removed without losing information.

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 simple read-only lookup with fully documented parameters and no output schema, the definition covers what the tool returns at a high level via the similarity score note. Minor gaps remain around result ordering and the seed track's own treatment in the response.

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%, with both required params given examples ('Weird Fishes' / 'Radiohead') and limit documented with bounds and a default. The description contributes no additional parameter meaning, so the baseline of 3 applies.

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 states a specific resource and result: similar tracks to a single track, plus the shape of the score. The phrase 'similar to one track' implicitly separates it from the sibling artist_get_similar and tag_get_similar without naming them, so the differentiation is clear enough to act on but not explicit.

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?

The parenthetical '(good for "more like this")' signals the intended recommendation use case. It stops short of stating when to choose this over artist_get_similar or tag_get_similar, and gives no prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.