Skip to main content
Glama

get_album_art

Retrieve the cover image for the currently playing VLC item or for a playlist item ID returned by get_playlist, so you can display or identify album art.

Instructions

Get the album art / cover image for the current item, or for a playlist item id from get_playlist.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_album_art"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. 'Get' implies a read-only, non-destructive call, but nothing is said about what happens when the item has no embedded art, whether the image is fetched from a remote service (latency/network dependency), or what form the payload takes.

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

Conciseness4/5

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

One compact sentence with the primary case ('current item') front-loaded and the parameterized case following. Nothing is wasted, though a few extra words on the return type would have been worth the space.

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-optional-parameter read tool with no output schema and no annotations, the definition covers the core semantics, but leaves the return format and the no-art case undefined. Those gaps matter because there is no output schema to fall back on.

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 coverage is 0% and the single parameter is optional with a null default, so the description must compensate. It does partially: it explains the id originates from get_playlist and that omission means 'the current item'. It does not clarify whether the id is a playlist index or a track identifier, nor the error behavior for an invalid id.

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 verb and resource ('Get the album art / cover image') and distinguishes two retrieval modes: the currently playing item versus a playlist entry. It is unambiguous what the tool returns conceptually, though it never says whether the art comes back as bytes, a URL, or a path.

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 by the two-mode phrasing: omit item_id for the current item, supply an id from get_playlist for a playlist entry. There is no explicit when-not guidance (e.g. what to do if no art exists, or whether this should be preferred over browse_folder for local files), so the agent must infer the boundaries.

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