Skip to main content
Glama
Sign In
MCP SteamOS Devkit

MCP SteamOS Devkit

by elliotttate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

adb_reverse

Reverse a TCP port from a SteamOS Devkit device to a host port, enabling connections from device to host via ADB.

Instructions

Reverse device tcp:DEVICE_PORT to host tcp:HOST_PORT with adb reverse.

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": {
      "device_port": "<device_port>",
      "host_port": "<host_port>"
    },
    "name": "adb_reverse"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialNo
host_portYes
device_portYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations provided, and the description only states the basic action. It does not disclose side effects, permissions required, or limitations of the reverse command.

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 description is a single sentence that conveys the core purpose. It is concise, though it could benefit from structured parameter details.

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

Completeness2/5

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

With 3 parameters (2 required) and an output schema (unseen), the description is too brief. It lacks return value info, parameter format, and usage examples.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no explanation of parameters beyond their names. The meaning of 'device_port', 'host_port', and 'serial' is not elaborated.

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?

The description clearly states the tool reverses a TCP connection from device to host, using specific ports. It uses a specific verb 'reverse' and resource format, differentiating it from sibling tools like adb_forward.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, or any conditions for use. Missing context about prerequisites or scenarios.

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