Skip to main content
Glama
kud

mcp-lastfm

by kud

get_user_weekly_album_chart

Retrieve a user's weekly album chart from Last.fm, specifying a week by Unix timestamps or defaulting to the latest chart.

Instructions

Get a user's album chart for a given week (or the latest)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoUnix timestamp — chart range end
fromNoUnix timestamp — chart range start
userNoLast.fm username; defaults to MCP_LASTFM_USERNAME when set, so it can be omitted for your own account
Behavior2/5

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

With no annotations, the description carries the full burden. It implies optional timestamps but does not disclose authentication needs, privacy restrictions, or output format. Minimal behavioral context beyond the basic purpose.

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?

Single sentence, front-loaded key information, no wasted words. Efficient and to the point.

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?

Adequate for a simple chart retrieval tool, but lacks details on what the chart contains, timestamp handling, and account prerequisites. With no output schema, more context would be helpful.

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 covers 100% of parameters with descriptions. The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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?

The description clearly states the action ('Get'), the resource ('a user's album chart'), and the temporal scope ('for a given week (or the latest)'). It distinguishes from sibling tools like get_user_weekly_artist_chart by specifying 'album'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. Does not explain when 'or the latest' applies, or how it differs from other weekly chart tools (e.g., get_user_weekly_chart_list).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kud/mcp-lastfm'

If you have feedback or need assistance with the MCP directory API, please join our Discord server