Skip to main content
Glama
Sign In
MCP Roku Control

MCP Roku Control

by charlysotelo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

press_key

Simulates pressing a remote button such as Home, Select, or VolumeUp to control your Roku TV with a single key press.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key_name": "<key_name>"
    },
    "name": "press_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
key_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavior. It only states it simulates a press, lacking details on prerequisites (e.g., active TV connection), side effects, or error conditions. Minimal behavioral insight.

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?

Concise paragraph with clear structure (description, Args list). Every sentence adds value. Minor improvement could be more structured formatting for AI parsing.

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

Completeness3/5

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

Covers the core action adequately. Missing return value description despite output schema existing, and no mention of prerequisites like device connection. Adequate but with gaps.

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?

Schema coverage is 0%, but description adds extensive meaning: lists examples, common keys, and special keys. This compensates well, though could include case sensitivity or exhaustive list.

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 it simulates a single button press on the TV remote, with specific verb and resource. It distinguishes from sibling tools like launch_app and power_on by focusing on key presses.

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?

Provides examples of common and special keys, giving clear context for use. However, it does not explicitly exclude alternatives like power_on for power keys, but the purpose is clear.

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