Skip to main content
Glama
Sign In
mcp-gtv

mcp-gtv

by kud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gtv_send_key

Send a single remote key press to control a Google TV device—navigate, adjust volume, power, and other remote functions.

Instructions

Send a single remote key press to the current device (navigation, media, volume, power…).

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": "<key>"
    },
    "name": "gtv_send_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesRemote key name, e.g. home, up, play

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'current device' but does not disclose error states, side effects, or whether the press is reliably delivered. Minimal behavioral context.

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?

Single sentence, no redundant words, front-loads the core action. Every word contributes to clarity.

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?

Given the tool's simplicity (1 enum param, no output schema), the description is adequate but lacks information about return value, error handling, or device state requirements. Could be more self-contained.

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 100% with enum values and a brief description. The description adds value by grouping keys into categories (navigation, media, volume, power), enriching the meaning beyond the raw 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 the verb 'send' and resource 'remote key press', specifying the scope to the current device and listing key categories (navigation, media, volume, power). It distinguishes from sibling tools like gtv_type_text and gtv_launch_app.

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?

The description implies usage (when a remote key press is needed) but provides no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or when not to use it.

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