Skip to main content
Glama

nowplaying

Report the current playback state of a Kodi instance, including media details, without modifying playback.

Instructions

Report what is playing on the target instance without changing anything — also a reachability and state probe. Returns the player-state snapshot { "state", "media", "id", "title", "artist", "time", "totaltime", … }; { "state": "stopped" } when idle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNoTarget Kodi instance. Omitted uses the default ("(null)").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYesPlayback state; "stopped" means nothing is loaded.
typeNoThe active player kind.
mediaNoReal media type (song/episode/movie/musicvideo/…); "unknown" for an off-library file.
idNoLibrary id of the playing item; -1 when off-library.
fileNoPath of the playing item.
labelNoKodi's display label for the item.
titleNoThe item's title (may be empty).
showtitleNoTV episode: the show's name.
seasonNoTV episode: season number.
episodeNoTV episode: episode number.
albumNoSong: the album name.
artistNoSong: the performers, an array of strings.
trackNoSong: track number on the album.
timeNoPlayback position { hours, minutes, seconds, milliseconds }.
totaltimeNoThe item's duration, same shape as time.
Behavior4/5

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

Without annotations, the description carries the full burden and effectively discloses the read-only nature, return format, and idle state handling.

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 efficiently convey purpose, behavior, and return format with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one optional parameter and an output schema, the description covers purpose, behavior, and return values adequately.

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 description does not add extra meaning beyond the schema's own parameter description.

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 clearly states the tool reports what is playing on the target instance and explicitly notes it does not change anything, distinguishing it from siblings like play, pause, or stop.

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?

The description implies it is safe and used as a reachability probe, but does not explicitly state when to use it versus alternatives like getplaylist or history.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/laszlopere/mcp-kodi'

If you have feedback or need assistance with the MCP directory API, please join our Discord server