Skip to main content
Glama
mcp-server-shieldtv
by SDNick484

Get what's playing

shield_get_now_playing
Read-only

Retrieve playback metadata and play state for the media currently active on the Shield, including app, title, subtitle, and position.

Instructions

Report what is playing: app, title, subtitle (artist or channel), play state, position in seconds.

<use_case> Retrieve playback metadata and playback state of media currently active on the Shield. </use_case>

<important_notes>

  • Requires ADB connection established via mcp-server-shieldtv adb-setup.

  • position_s is null for live streaming TV. </important_notes>

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
appYes
stateYes
titleYes
subtitleYes
position_sYes
app_packageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds value beyond them with a hard prerequisite (ADB connection via `mcp-server-shieldtv adb-setup`) and a field-level caveat (position_s is null for live streaming TV). It does not state what happens when nothing is playing (empty result vs error), which is the remaining behavioral gap.

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?

The lead sentence is front-loaded and every clause carries information, and the tagged sections make the prerequisite easy to scan. The <use_case> sentence largely restates the opening line ('playback metadata and playback state'), which is mild redundancy rather than bloat.

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?

With an output schema present, the description need not explain return values, yet it does so anyway while also covering the setup prerequisite and the live-TV null case. For a zero-parameter read tool, an agent has everything needed to call it correctly.

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 nothing for the description to disambiguate; the baseline of 4 applies. The mention of position_s is about output rather than input, so it adds no parameter meaning.

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 opens with a specific verb and resource ('Report what is playing') and enumerates exactly what is returned: app, title, subtitle, play state, and position in seconds. That level of specificity makes it distinguishable from neighbors such as shield_get_status or shield_list_apps without opening either schema.

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

Usage Guidelines4/5

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

The <use_case> block gives clear context — retrieve playback metadata and playback state of media currently active on the Shield — so an agent knows when this is the right call. It stops short of naming exclusions or alternatives (e.g. when to prefer shield_get_status), so it is clear but not fully routing.

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