Skip to main content
Glama
Sign In
MCP SteamOS Devkit

MCP SteamOS Devkit

by elliotttate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

adb_unreal_insights_setup

Configures an Android device's tracehost and reverse TCP port for Unreal Insights connection.

Instructions

Set Unreal's Android tracehost property and reverse tcp:1981 for Unreal Insights.

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": "adb_unreal_insights_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNo
serialNo
tracehostNo127.0.0.1

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description must fully disclose behavior. It states the action (set property and reverse port) but omits side effects, permissions, error conditions, or whether the operation is safe. For a tool that modifies device settings, this is insufficient.

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?

A single 12-word sentence is highly concise and front-loaded. However, it omits important details, so conciseness trades off against completeness. Still, it avoids unnecessary verbiage.

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?

Despite having an output schema, the description lacks context about prerequisites (e.g., device connected), state changes, or failure modes. With three optional parameters and no schema descriptions, the description is too sparse to fully guide correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain the parameters (port, serial, tracehost). While 'tracehost' and reverse tcp:1981 are mentioned, the default values and meaning of 'serial' are unclear. The description adds minimal value over the schema's property names.

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 verb 'Set' and the specific resources: 'Unreal's Android tracehost property' and 'reverse tcp:1981'. It distinguishes the tool from siblings like adb_forward or adb_reverse by its focus on Unreal Insights setup, though it could be more explicit about its unique role.

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 vs. alternatives (e.g., adb_forward, adb_reverse). The description does not mention prerequisites, typical scenarios, or limitations, leaving the agent without context for appropriate invocation.

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