Skip to main content
Glama
Sign In
nvidia-MCP

nvidia-MCP

by glasgowm148
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

shield_connect

Connects ADB to the configured NVIDIA Shield TV and prompts you to accept its on-TV debugging request.

Instructions

Connect ADB to the configured Shield only. Accept its debugging prompt on the TV.

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_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the mutation and open-world profile is covered. The description adds genuinely useful context not in the annotations: it requires physically accepting a debugging prompt on the TV. It does not mention state changes, failure modes, or prerequisites like ADB availability.

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 short sentences, no redundancy, with the core action front-loaded and the TV-side prerequisite immediately after. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be described, and annotations cover the safety profile. The description supplies the key operational prerequisite (accepting the TV debugging prompt), leaving only minor gaps such as what happens on connection failure or whether an existing session is reused.

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 per the rubric the baseline is 4. Schema coverage is 100% and there is nothing further the description could clarify about inputs.

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?

States a specific verb ('Connect ADB') and resource ('the configured Shield') plus a scoping constraint ('only'), so it is easily distinguished from read-oriented siblings like shield_status or shield_remote. It stops short of naming an alternative or contrasting with the other shield_* tools.

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?

'Only' hints that this is the sole connection path, and the TV-prompt sentence implies a first-run/precondition context. There is no explicit when-to-use vs. when-not guidance or reference to a sibling for a related task, so usage is only implied.

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

Deploy Server

Other Tools