Skip to main content
Glama
AaronGoldsmith

MCP Remote Control

by AaronGoldsmith
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HOST_IPYesThe IP address of the Roku TV (e.g., 192.168.1.100). This can be found in Settings > Network > About on your TV.

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
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
press_keyA

Simulates a single button press on the TV remote.

Args:
    key_name: The name of the key to press (e.g., Home, Select, VolumeUp). 
              Common keys are Home, Back, Select, Up, Down, Left, Right.
              Special keys are: PowerOn, PowerOff, VolumeUp, VolumeDown, VolumeMute
launch_appA

Launches an application on the TV using its name.

Args:
    app_name: The name of the app to launch (e.g., Netflix, YouTube, Hulu).
              Case-insensitive. Use list_apps() to see available apps.
list_appsA

Lists all available apps and their corresponding Roku channel IDs.

Returns a formatted list of app names and their IDs that can be used with launch_app().
get_device_infoA

Retrieves basic device information (model, software version, etc.) as XML.

power_onA

Powers on the TV.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: get_device_info retrieves device metadata, list_apps enumerates available applications, launch_app starts a specific app, power_on turns on the TV, and press_key simulates remote button presses. The descriptions explicitly differentiate their functions, eliminating any ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: get_device_info, list_apps, launch_app, power_on, and press_key. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.

Tool Count5/5

With 5 tools, this server is well-scoped for remote control functionality. Each tool serves a specific, essential purpose (device info, app management, power control, and key simulation), and none feel redundant or missing for basic TV operations. The count is appropriate for the domain.

Completeness4/5

The tool set covers core remote control operations effectively, including power management, app launching, and key presses. However, minor gaps exist, such as the lack of a power_off tool (though press_key can simulate PowerOff) and no explicit volume control beyond key presses, which agents can work around but might slightly hinder seamless automation.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources