Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
tv_playA

Search for and play content on the TV. Handles deep linking, force-stops, and profile selection automatically. Use for shows, movies, and music.

tv_powerA

Control TV power. Actions: on (wake + WOL if needed), off (standby), toggle, status

tv_volumeA

Control TV volume. Actions: up, down (repeatable with steps), mute, unmute, set (absolute level via ADB key repeats)

tv_keyA

Send a remote control key press to the TV. Keys: up, down, left, right, center, back, home, play, pause, play_pause, stop, next, previous, fast_forward, rewind, volume_up, volume_down, mute, power, sleep, wakeup

tv_appA

Launch an app on the TV by name. Available: youtube, youtube_music, youtube_kids, netflix, disney, prime, spotify, jellyfin, skyshowtime, hbo. Does not handle deep links or profiles — use tv_play for that.

tv_searchA

Search for content across streaming services without playing. Returns available services and deep links. Use type "music" for Spotify track search.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 6 tools

Disambiguation4/5

Most tools have clear boundaries: tv_play handles playback with deep linking, tv_search only returns results, tv_app launches apps without deep linking, and tv_key sends raw key presses. Some overlap exists between tv_volume and tv_key (both can send volume commands), and tv_play/tv_app can both launch content, but descriptions clarify when each should be used.

Naming Consistency4/5

All tools follow a consistent tv_ prefix and snake_case convention, making the set predictable. The second part is mostly an action noun (power, volume, key, app) rather than a strict verb_noun pattern, but the naming remains coherent and easy to navigate.

Tool Count5/5

Six tools is a well-scoped set for a TV remote control server. Each tool covers a distinct major function: playback, power, volume, key input, app launching, and search — no unnecessary bloat or redundant duplicates.

Completeness4/5

The core remote control lifecycle is well covered: power, volume, navigation, playback, app launch, and content discovery. Obvious gaps like input/source switching or querying current playback status are missing, but the tool surface is still sufficient for most common TV control workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues