Skip to main content
Glama
Sign In
Apple TV MCP

Apple TV MCP

by trevor-nichols
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

apple_tv_open_app

Idempotent

Launch an installed app by exact bundle ID or exact display name on Apple TV. Deterministic matching prevents typos from opening a similar app.

Instructions

Launch an installed application by exact bundle ID or exact display name.

Matching is deterministic. Typos do not auto-launch a similar application.

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": {
      "app": "<app>"
    },
    "name": "apple_tv_open_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesExact bundle identifier, or exact application display name.

Output Schema

NameRequiredDescriptionDefault
nameNo
launchedYes
bundle_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the safety profile (non-readOnly, idempotent, non-destructive), so the bar is lower. The description adds genuine behavioral context beyond annotations by stating matching is deterministic and typos will not auto-launch a similar app, clarifying the failure mode.

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?

Two short sentences, front-loaded with the core action and the exact-matching constraint. Every sentence earns its place with no filler.

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

Completeness4/5

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

An output schema exists so return values need not be explained, and annotations cover the safety profile. The description contributes the key determinism behavior, though it could mention prerequisites such as resolving the app via apple_tv_list_apps.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter is fully documented in the schema itself. The description restates 'exact bundle ID or exact display name' but adds no syntax or format detail beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Launch') and resource ('an installed application'), which cleanly distinguishes it from siblings like apple_tv_open_url (URLs) and apple_tv_list_apps (enumeration). It does not explicitly name a sibling to route against, so it falls just short of the top mark.

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 when to use it (launching an installed app) but gives no explicit when/when-not guidance or pointers to alternatives such as using apple_tv_list_apps first to resolve a valid bundle ID. Usage context is only implied.

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