Skip to main content
Glama

tv_display

Transform your TV into a digital signage display showing dashboards, clocks, messages, or custom web content. Serves HTML locally and opens it in the TV browser for smart home visualization.

Instructions

Turn the TV into a display — show dashboards, messages, clocks, or any URL.

The TV becomes a smart display. HTML is generated and served locally, then opened in the TV's browser.

Args: content_type: "message", "clock", "dashboard", "photo", "iframe", or "custom". data: Content-specific data: - message: {"text": "Hello!", "bg": "#000", "color": "#fff"} - clock: {"format": "24h"} or {"format": "12h"} - dashboard: {"title": "Home", "cards": [{"label": "Temp", "value": "22°C"}]} - photo: {"urls": ["http://..."], "interval": 5} - iframe: {"url": "https://...", "fullscreen": true} - custom: {"html": "..."} tv_name: Target TV. Omit for default. port: Local server port (default 8765).

Examples: tv_display("message", {"text": "Dinner's ready!"}) tv_display("clock") tv_display("dashboard", {"title": "Home", "cards": [{"label": "Time", "value": "21:30"}]}) tv_display("iframe", {"url": "https://grafana.local/d/stats"})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
content_typeYes
dataNo
tv_nameNo
portNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses critical implementation detail (local HTML server on specified port) not inferable from schema, though omits whether this interrupts existing TV sessions.

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?

Well-structured with clear Args/Examples sections; examples are verbose but essential given the unstructured 'anyOf' data schema, making every sentence earn its place.

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

Completeness5/5

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

Fully complete given presence of output schema and complex polymorphic data parameter which is thoroughly explained with concrete examples for each content type.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Completely compensates for 0% schema description coverage by exhaustively documenting content_type options, data payload shapes per type, and default behaviors for optional params.

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?

Opens with specific action ('Turn the TV into a display') and clearly distinguishes from media-playing siblings (tv_play, tv_cast) by emphasizing dashboards, HTML generation, and browser-based display.

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?

Implies clear usage context through content examples (dashboards vs. video), though lacks explicit 'when not to use' comparisons to tv_cast or tv_play.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Hybirdss/smartest-tv'

If you have feedback or need assistance with the MCP directory API, please join our Discord server