Skip to main content
Glama
lastfm-taste-mcp

lastfm-taste-mcp

by nurasik14

tag_get_similar

Read-only

Find related Last.fm tags for a given tag (e.g., chill to chillout or downtempo) to broaden music discovery when direct tag matches are sparse.

Instructions

Tags related to a tag (e.g. chill → chillout, downtempo). Last.fm often returns nothing here.

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": {
      "tag": "<tag>"
    },
    "name": "tag_get_similar"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYesTag name, e.g. 'chill', 'lo-fi', 'shoegaze'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint already establishes this is a safe read, so the description's added value is the disclosure that the upstream API frequently yields empty results — a genuinely useful behavioral trait an agent cannot infer from annotations or schema. It does not cover ordering, weighting, or result-size limits, keeping it below a 5.

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?

Two short sentences, zero filler, and the core behavior is front-loaded ahead of the empty-result caveat. Every sentence carries information the agent needs.

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-parameter read-only tool with full schema coverage and no output schema, the description covers what it returns conceptually (related tags) and the main failure mode (empty results). A note on result volume or whether similarity is weighted would close the remaining gap.

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% and the single 'tag' parameter is already documented with its own examples ('chill', 'lo-fi', 'shoegaze'). The description's example ('chill') overlaps with that without adding format, casing, or normalization rules, so the baseline 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 gives a specific verb-and-resource framing ('Tags related to a tag') plus a concrete example ('chill → chillout, downtempo') that makes the semantics unmistakable and separates it from tag_get_info or tag_get_top_artists by implication. It stops short of explicitly naming a sibling, so it lands at a strong 4 rather than a 5.

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?

There is no explicit when-to-use or when-not-to-use statement, but the caveat 'Last.fm often returns nothing here' functions as a practical usage signal telling the agent to expect empty results and fall back elsewhere. That is implied guidance rather than a routing rule, so a 3 is appropriate.

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