Skip to main content
Glama
Sign In
Sonora MCP

Sonora MCP

by encodi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Now playing

now_playing
Read-only

Retrieve the track or episode currently playing on a user's Spotify account, including playback progress and active device, to answer real-time listening status queries.

Instructions

Get what is currently playing on the user's Spotify account (track or episode, progress and device).

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0-dev

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds useful behavioral context by enumerating what the response reports (track or episode, progress, device), but says nothing about authentication requirements, rate limits, or the empty/no-active-playback case.

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 front-loaded sentence with the resource first and the return contents in parentheses. There is no filler, no restatement of the title, and nothing that could be cut without losing information.

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 zero-param, read-only lookup with annotations covering safety, the description is nearly complete: it tells the agent what is fetched and what fields come back. The remaining gap is the degenerate case (no active playback) and whether a specific account/auth context is required, which matters for an openWorld tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain; baseline for a no-arg tool applies. The description correctly avoids inventing argument behavior and instead spends its words on the result.

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?

States a specific verb ('Get') and resource ('what is currently playing on the user's Spotify account') and even names the return shape (track or episode, progress, device). That makes it easy to distinguish from siblings like search and list_devices in practice, though it never explicitly contrasts itself with them.

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 only implied by the name and the word 'currently' — an agent can infer this is the polling-style call for live playback state versus search or device listing. There is no explicit when-to-use/when-not statement, no mention of prerequisites such as an active authenticated session, and no note on what to do when nothing is playing.

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