Skip to main content
Glama

FoxAPIs data sources

Last.fm artist

lastfm_artist
Read-onlyIdempotent

A Last.fm artist: listeners, play count, top tags and similar artists, from the artist name. Costs 1 credit a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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": "lastfm_artist"
  }
}

Input Schema

NameRequiredDescriptionDefault
artistYesFor example: "Radiohead"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a safe, idempotent, open-world read, so the bar is lower. The description adds genuinely new operational context not present in structured fields: a 1-credit cost per call, no charge when no data is returned, and a required FoxAPIs key.

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 dense sentence that front-loads the resource and payload, then tacks on cost and auth in the same breath. Nothing is redundant or padded.

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?

With no output schema, the description correctly compensates by listing the returned fields, and it covers cost and auth prerequisites. It stops short of describing response structure (e.g., image URLs, tag weights) or error behavior such as unknown artists, which would round it out.

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?

There is only one parameter and the schema already carries a full example ('Radiohead') with 100% description coverage. The phrase 'from the artist name' restates the schema rather than adding format rules (e.g., disambiguation of same-named artists).

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 names a specific resource (Last.fm artist) and enumerates exactly what is returned: listeners, play count, top tags and similar artists, keyed by artist name. Naming Last.fm also implicitly separates it from soundcloud_artist and similar siblings, though it does not call out the distinction 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 only through 'from the artist name', which tells the agent the single input but not when to prefer this over another artist-style lookup. There are no when-not conditions or named alternatives, so an agent must infer fit from the resource name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources