Skip to main content
Glama

now_playing

Shows the currently playing track with title, artist, album, and cover art availability, answering 'what is this' rather than playback position or status.

Instructions

What is playing, described the way a person would: title, artist, album, and whether there is any picture (an embedded cover is not video). Use this rather than get_status when the question is 'what is this', and get_status when it is 'where are we'.

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

Input Schema

NameRequiredDescriptionDefault
coverNoAlso extract the embedded cover art and return its path on disk. Costs one ffmpeg run the first time per file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden and does useful work: it clarifies that an embedded cover does not count as video, which prevents a real misclassification. It omits the behavior when nothing is playing and says nothing about the ffmpeg cost of cover extraction, leaving the schema to explain that side effect.

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?

Two sentences, front-loaded with the primary question, and the routing rule is compressed into a single parallel clause. There is no filler, and the parenthetical clarification earns its place by preventing a misread.

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?

Without an output schema, the description must convey the return shape, and it does by naming the fields returned. It is slightly incomplete for edge cases such as no active media or failures, but the tool is simple enough that the core contract is clear.

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 100% and the single `cover` parameter is already documented in the schema, including the ffmpeg cost. The description only hints at it via 'whether there is any picture,' so the schema does the heavy lifting and the baseline applies.

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 gives a specific verb and resource ('what is playing') and enumerates the returned fields (title, artist, album, picture presence), so an agent knows exactly what the tool yields. It explicitly positions itself against `get_status` by question type, so the boundary with the sibling is unambiguous.

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

Usage Guidelines5/5

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

It states both when to use this tool ('what is this') and when to use the alternative ('where are we' -> `get_status`), with the selecting condition spelled out in plain terms. Nothing is left to inference about routing.

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

Deploy Server

Other Tools