tv-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesA | List configured and live-discovered Samsung (Tizen) / LG (webOS) TVs with reachability. |
| connect_deviceB | Connect to a TV by configured name or by host+platform. Unlocks app lifecycle tools. |
| docsA | Deep docs for platform pain points (signing, dev mode, packaging, pairing). Call without a topic to list topics. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| docs-device-setup | |
| docs-tizen-signing | |
| docs-webos-dev-mode | |
| docs-webos-packaging | |
| docs-remote-key-pairing |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: discover devices, connect to a device, and access documentation. There is no overlap or ambiguity between these three tools.
list_devices and connect_device follow a verb_noun pattern, but docs breaks the pattern by using a noun alone without a verb prefix like get_docs or list_topics.
With only 3 tools and all descriptions mentioning that connecting 'unlocks app lifecycle tools', the server appears to gate functionality behind an initial connection step rather than exposing it directly. The set feels thin for a TV control server that presumably supports app lifecycle, pairing, and packaging operations that are only referenced in the docs tool.
The tool surface only covers discovery, connection, and documentation. Descriptions reference 'app lifecycle tools', 'pairing', 'dev mode', and 'packaging' as capabilities, but no tools exist to actually perform these operations—only docs describing them. This is a severely incomplete surface for the implied domain.