lastfm_search_artists
Search Last.fm for artists by name. Returns matching results with artist metadata.
Instructions
Search for artists on Last.fm.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| artist | Yes | ||
| limit | No | ||
| api_key | No |
Search Last.fm for artists by name. Returns matching results with artist metadata.
Search for artists on Last.fm.
| Name | Required | Description | Default |
|---|---|---|---|
| artist | Yes | ||
| limit | No | ||
| api_key | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, and the description fails to disclose behavioral aspects such as authentication requirements (implied by api_key), rate limits, pagination, or result format, leaving agents uninformed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, but it lacks necessary detail; it is under-specified rather than efficiently concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a search tool with required api_key and no output schema, the description omits crucial context about authentication, result structure, and potential errors, leaving the agent underinformed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description does not explain any of the three parameters, missing the opportunity to clarify the 'limit' parameter or the purpose of 'api_key'.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (search) and resource (artists) on Last.fm, distinguishing it from sibling tools like lastfm_artist_info which gets details for a specific artist.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance provided on when to use this tool versus other Last.fm tools like lastfm_artist_info or lastfm_similar_artists, ignoring the context of numerous sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/malamutemayhem/unclick'
If you have feedback or need assistance with the MCP directory API, please join our Discord server