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

Check Bluetooth remotes

shield_get_remotes
Read-only

Lists Bluetooth remotes paired to an NVIDIA Shield and reports whether each works or is stuck, helping diagnose unresponsive physical or hub remotes.

Instructions

List the Shield's Bluetooth remotes (e.g. a Harmony hub) and whether each works.

<use_case> Diagnose unresponsive physical or hub remotes paired to the Shield over Bluetooth. </use_case>

<important_notes>

  • Requires ADB connection (mcp-server-shieldtv adb-setup).

  • Reports "stuck" state when a connected remote stops sending button events (common after sleep/reboot). </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_remotes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
adviceYes
remotesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: an ADB prerequisite and the 'stuck' state that appears when a connected remote stops sending button events after sleep/reboot. It does not describe the shape of the reported status values, but the output schema covers returns.

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?

One summary sentence followed by clearly labeled use-case and important-notes blocks. Every line carries information the agent needs (prerequisite, diagnostic scenario, the 'stuck' interpretation), with no repetition of name or title.

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 simple 0-param, read-only tool with a dedicated output schema, the description covers the remaining gaps: what it lists, why an agent would call it, the ADB setup requirement, and how to read a commonly confusing result state. Nothing needed to invoke it correctly is missing.

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 nothing for the description to disambiguate; the baseline for a 0-param tool applies. The description instead spends its words on prerequisites and output meaning, which is the right allocation.

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: 'List the Shield's Bluetooth remotes ... and whether each works.' The health-check aspect plus the Harmony-hub example makes the scope unambiguous, and the sibling tools (apps, now-playing, power, key-send) are clearly different operations, so no disambiguation is needed.

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 concrete when-to-use condition: diagnosing unresponsive physical or hub remotes paired over Bluetooth. It does not name a distinct alternative tool or state when not to use it, which keeps it short of a 5.

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