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

Reboot the Shield

shield_reboot
Destructive

Restart an NVIDIA Shield TV when the device is unresponsive or a cold reset is needed, such as for unresponsive remotes. Requires an ADB connection.

Instructions

Restart the Shield TV.

<use_case> Reboot the device when software is unresponsive or remotes require a cold reset. </use_case>

<important_notes>

  • Disruptive: stops active playback and disconnects network services.

  • Rate limited to 1 reboot per 120s to prevent rapid boot loops.

  • Requires ADB connection (mcp-server-shieldtv adb-setup). </important_notes>

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "shield_reboot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
sentYes
adviceYes
detailYes
outcomeYes
remotesYes
back_after_sYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructive=true and idempotent=false, but the description adds substantive context: active playback is interrupted, network services disconnect, reboots are rate limited to one per 120s to avoid boot loops, and an ADB connection is a prerequisite. These are exactly the operational facts an agent needs before invoking a destructive device action.

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 sentences plus two tight bulleted notes; the disruptive effect is stated before the rate limit and setup requirement, so risk is front-loaded. Every line conveys an operational fact with no filler.

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?

For a no-argument destructive device action with an output schema already documenting returns, the description covers disruption, throttling, and the ADB prerequisite. Nothing an agent needs in order to call it safely is absent.

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?

The tool takes zero parameters, so the schema carries the full structural burden and there is nothing for the description to disambiguate. The baseline for a zero-parameter tool applies, with no added or missing parameter meaning.

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?

"Restart the Shield TV" gives a specific verb plus resource, and the use_case reinforces it as a device-level cold restart. It does not explicitly distinguish itself from the power-related sibling, so an agent must still infer whether shield_set_power could achieve the same end.

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 states clear triggering conditions: unresponsive software or remotes needing a cold reset. There is no explicit when-not guidance or named alternative (e.g., a softer power-cycle via shield_set_power), which keeps it just short of the top score.

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