Skip to main content
Glama

Get an artist

get_artist
Read-onlyIdempotent

One artist, with their song count and picture image_url is the picture uploaded for it (null without one); while it has none, image_fallback is the cover of its newest song still there that has one (song_id, preview_url 640 px and thumbnail_url 160 px WebP), to show in its place, or null without such a song. It is read-only, never saved as the picture, and follows the newest song (a new song or an archived one changes it).

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_id": "<artist_id>"
    },
    "name": "get_artist"
  }
}

Input Schema

NameRequiredDescriptionDefault
artist_idYesThe artist id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent and non-destructive, but the description adds real semantics beyond them: image_url is the uploaded picture, image_fallback is a derived cover from the newest song that has one, the fallback is never persisted, and it tracks the newest song as songs are added or archived. That is genuine behavioral context an agent could not infer from annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded with the artist and its fields, but it is delivered as one long run-on sentence with tangled phrasing ('picture image_url is the picture uploaded for it ... while it has none'). The information is valuable but the structure makes it slower to parse than necessary.

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 tool with no output schema, the description does the heavy lifting on the non-obvious return values (image_url vs. image_fallback and their null conditions). It omits error/not-found behavior and the artist's other fields, which is a minor but real 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?

Only one parameter and schema description coverage is 100%, so the schema already fully documents artist_id. The description adds no format, sourcing, or lookup semantics for the id, so the baseline 3 is appropriate.

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 the resource (one artist) and the notable returned fields (song count, picture, fallback cover), so the agent knows this is a single-artist fetch rather than a list or mutation. It does not explicitly contrast with siblings like get_song, but the verb+resource is recoverable and the returned-data focus is specific.

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?

There is no when-to-use guidance, no mention of alternatives, and no note about what happens for a missing or invalid artist_id. The only usage-adjacent statement is 'It is read-only', which is behavioral rather than routing guidance.

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