Skip to main content
Glama
mcp-server-shieldtv
by SDNick484

Launch an app

shield_launch_app
Idempotent

Launches a streaming app on NVIDIA Shield TV by friendly name, confirms it runs in the foreground, and suggests closest matches for unknown app names.

Instructions

Launch an application on the Shield TV.

<use_case> Launch streaming media apps (e.g. Netflix, YouTube, Plex) by friendly name. </use_case>

<important_notes>

  • Video output requires Onkyo AVR input set to 'strm-box' and TV input set to AVR HDMI port.

  • Confirms that the application is running in the foreground before returning.

  • Unknown app names suggest closest matches from configured apps. </important_notes>

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": "shield_launch_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesFriendly app name from shield_list_apps, e.g. 'netflix'.

Output Schema

NameRequiredDescriptionDefault
sentYes
detailYes
shieldYes
outcomeYes
warningsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior. The description adds genuinely new traits: an external hardware prerequisite (Onkyo AVR set to 'strm-box', TV on the AVR HDMI port), blocking semantics (returns only after confirming foreground state), and fuzzy matching that suggests the closest configured app when the name is unknown — a behavior that could launch the wrong app and is otherwise undisclosed.

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?

Front-loaded with the core action and organized into tightly scoped use_case and important_notes blocks; every bullet carries actionable information. The use_case line partially restates the opening sentence, a minor redundancy.

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?

An output schema exists, so return values need no explanation, and the description still covers the one return-relevant behavior (foreground confirmation). Prerequisites, name sourcing, and fuzzy-match behavior are all covered for a single-parameter tool.

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%, so the schema already documents the single 'app' parameter, making 3 the baseline. The description adds real meaning beyond it by specifying where valid names come from (shield_list_apps) and how unresolvable names are resolved (closest-match suggestions).

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?

States a specific verb and resource ('Launch an application on the Shield TV') and the use_case block narrows it to streaming media apps addressed by friendly name. The reference to shield_list_apps as the source of valid names implicitly separates it from the enumeration sibling.

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?

The use_case block gives clear context for when to use it and the important_notes point the agent at shield_list_apps for valid names. There are no explicit exclusions or when-not-to-use conditions, but no plausible alternative exists among the siblings for launching.

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