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

Wake or sleep the Shield

shield_set_power
Idempotent

Wake or sleep an NVIDIA Shield TV by setting its power state to 'on' or 'off', using discrete commands that return unchanged if already in the requested state.

Instructions

Wake the Shield ('on') or put it to sleep ('off').

<use_case> Manage device power state. </use_case>

<important_notes>

  • Uses discrete WAKEUP and SLEEP commands rather than ambiguous toggles.

  • Idempotent: returns 'unchanged' if already in requested state. </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": {
      "state": "<state>"
    },
    "name": "shield_set_power"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes

Output Schema

NameRequiredDescriptionDefault
sentYes
detailYes
shieldYes
outcomeYes
warningsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description largely restates idempotency, though it does add the concrete return token ('unchanged') if the device is already in the requested state. The note about using discrete WAKEUP and SLEEP commands rather than a toggle is extra mechanism context of modest value. It adds some useful detail beyond annotations but not rich behavioral context such as failure handling or confirmation requirements.

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?

The power action is stated first and the supporting notes are short and clearly separated. The 'ambiguous toggles' remark is slightly self-congratulatory filler that could be trimmed, but nothing is long-winded.

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 one-parameter, single-purpose power switch with an output schema and full annotation coverage, the definition supplies everything needed to call it correctly. There are no nested objects or complex return semantics that require further explanation.

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 description coverage is 0%, but the only parameter is an 'on'/'off' enum whose meaning the description explicitly defines as wake and sleep. That is close to the most meaning that can be added for a single binary switch, leaving only trivial ambiguity.

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?

The description opens with a specific verb-resource pair, 'Wake the Shield ('on') or put it to sleep ('off')', and maps each enum value to its real-world effect. This clearly separates it from siblings such as shield_reboot or shield_send_key, which an agent can rule out without opening another schema.

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 <use_case> block says 'Manage device power state', which implies the context of use but does not state when to choose this over shield_reboot or any other power-adjacent sibling, nor any preconditions. Guidance is present but generic, leaving the agent to infer the boundary cases.

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