StreamXpress MCP Server

Overview Schema Source Related Servers Discussions Admin

select_port

Choose a physical output port on a DekTec device for TS stream playout. Provide device serial and port number to set the active output.

Instructions

Select a physical output port for playout.

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": {
      "serial": "<serial>",
      "port_num": "<port_num>"
    },
    "name": "select_port"
  }
}

Input Schema

Name	Required	Description
`serial`	Yes	Device serial number (from scan_ports)
`port_num`	Yes	Physical port number on the device
`modulation`	No	Initial modulation standard (0=none, use SPRC.MOD_* constants)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 6, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations are absent, so the description must carry the burden of behavioral disclosure. It does not explain whether this operation mutates state, has side effects, or requires specific conditions. The single sentence adds no transparency beyond what 'select' implies.

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?

The description is a single clear sentence with no redundant words. It is appropriately sized for a straightforward selection tool.

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

Completeness3/5

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

The presence of an output schema reduces the need to explain return values. The schema also documents prerequisites (serial from scan_ports). However, the description alone does not place the tool within a broader setup workflow or mention potential side effects, leaving some gaps.

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

Parameters3/5

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

The input schema covers 100% of parameters with descriptions, so the baseline is 3. The description itself adds no parameter-specific meaning, but the schema already provides sufficient details such as 'serial from scan_ports' and 'modulation standard'.

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 uses a specific verb ('select') and resource ('physical output port for playout'), clearly indicating the tool's function. It differentiates from sibling tools like scan_ports and connect by focusing on choosing an output port for playout.

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 is provided on when to use this tool or how it fits into a workflow. The schema mentions 'serial' comes from scan_ports, but the description itself does not reference prerequisites, alternatives, or sequencing.

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

Deploy Server