eos-mcp-server

Select Eos Channel

eos_select_channel

Read-onlyIdempotent

Select a lighting channel on the EOS console to set the target for subsequent adjustments or wheel nudges. This command changes the active channel without altering its current level.

Instructions

Select a channel on the command line without changing its level. Use this before eos_adjust_parameter or eos_nudge_wheel, which act on whatever is currently selected.

Args:

channel (number): Channel number to select.

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": {
      "channel": "<channel>"
    },
    "name": "eos_select_channel"
  }
}

Input Schema

Name	Required	Description	Default
`channel`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already mark read-only/idempotent, but description adds that selection is a persistent command-line state and explicitly states no level change. This clarifies side-effect-free behavior beyond the hints.

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 compact, front-loads the action, then gives usage direction and an argument list. No redundant sentences.

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 one-parameter, no-output tool, description plus annotations fully cover purpose, usage, and side effects. Sibling references provide adequate context.

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?

The description only restates 'channel (number): Channel number to select,' which duplicates the schema's integer type and minimum. It adds no behavioral meaning like what the channel number refers to or how selection manifests.

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?

Description uses specific verb 'Select' and states scope: 'a channel on the command line without changing its level,' clearly distinguishing from level-setting tools like eos_set_channel_level. The resource and action are unambiguous.

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

Usage Guidelines5/5

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

Explicitly instructs to use before eos_adjust_parameter or eos_nudge_wheel, explaining these act on 'whatever is currently selected.' This names specific sibling alternatives and defines the prerequisite context.

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

Deploy Server