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

Get Shield status

shield_get_status
Read-only

Check Shield TV power state, reachability, foreground app, and volume before sending commands so you act on current data.

Instructions

Start here. Query Shield TV power state, reachability, foreground app, and volume.

<use_case> Inspect Shield TV power, connectivity, active foreground package, and volume before issuing commands. </use_case>

<important_notes>

  • When unreachable, stale is true and values represent last known state.

  • Video output routes to the Onkyo AVR input 'strm-box'. </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_get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
hostYes
nameYes
as_ofYes
errorYes
powerYes
staleYes
deviceYes
pairedYes
volumeYes
dry_runYes
reachableYes
current_appYes
current_app_packageYes

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 cover the read-only, closed-world safety profile, yet the description adds real behavioral context beyond them: when the device is unreachable, stale is true and values are last-known rather than live. The note that video output routes to the Onkyo AVR input 'strm-box' is useful operational context. It does not describe latency, caching, or failure modes beyond staleness, so it falls short of a 5.

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 'Start here' and a one-line summary, then structured tags for use case and notes. The only waste is that the use_case sentence largely restates the opening line (power, connectivity, foreground package, volume), which could be trimmed.

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-value detail is unnecessary, and annotations carry the safety profile. What remains — entry-point role, staleness semantics, and the AVR routing dependency — is fully covered, leaving nothing an agent needs before calling it.

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 there is no parameter meaning to add and the baseline is 4. The description correctly spends no space on arguments and instead documents the returned state fields.

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 first line states a specific verb (query) and names exactly what is returned: power state, reachability, foreground app, and volume. 'Start here' plus 'before issuing commands' positions it against the command-oriented siblings like shield_send_key and shield_set_power without needing to open their schemas.

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 a clear condition: inspect state before issuing commands, which is exactly the decision an agent faces. It stops short of explicit exclusions (e.g. 'use shield_get_now_playing for media metadata'), so it is clear context rather than full when/when-not guidance.

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