eos-mcp-server

Fire Eos Cue

eos_fire_cue

Destructive

Fire any cue immediately by providing its cue list and number, even out of sequence. Sends the command to the console and returns confirmation.

Instructions

Fire a specific cue immediately, regardless of playback sequence (equivalent to selecting it and pressing Go, but works even if it's out of order).

Args:

cue_list (number): Cue list number the cue lives in.
cue_number (string): Cue number, e.g. "5" or "12.5" for a numbered part.

Returns confirmation text once the OSC message is sent. Eos does not send a synchronous acknowledgement, so success here means "the command was sent," not "the cue finished." Use eos_get_status to check playback position afterward.

Example: cue_list=1, cue_number="5" fires cue 5 in cue list 1.

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": {
      "cue_list": "<cue_list>",
      "cue_number": "<cue_number>"
    },
    "name": "eos_fire_cue"
  }
}

Input Schema

Name	Required	Description	Default
`cue_list`	Yes	Cue list number
`cue_number`	Yes	Cue number, e.g. "5" or "12.5"

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds important behavioral context beyond annotations by disclosing that return means the OSC message was sent, not that the cue finished, and that Eos provides no synchronous acknowledgement. This is significant because the tool is marked destructive/readOnly=false, and the async caveat helps set correct expectations.

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 front-loaded with the main purpose, then organized into Args, Returns, and Example sections. It is concise and every section contributes useful information, though the Args section somewhat duplicates the schema.

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 two-parameter tool, the description is complete: it explains the action, its sequencing flexibility, the return value, the asynchronous nature, suggests a follow-up tool, and provides an example. Given the schema and annotations, no critical context is missing.

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 already covers both parameters thoroughly, including examples for cue_number. The description largely repeats this information, adding only the 'numbered part' clarification and a worked example, which is marginal value over the schema.

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?

The description uses the specific verb 'Fire' with the resource 'specific cue' and clarifies that it works 'regardless of playback sequence,' which differentiates it from sequential tools like eos_go or selection tools like eos_select_cue. It clearly states what the tool does and its distinctive out-of-order capability.

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

Usage Guidelines4/5

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

The description explicitly notes when to use the tool ('works even if it's out of order') and recommends eos_get_status afterward to verify playback position. It does not explicitly name alternatives like eos_go for sequential playback, so it lacks full exclusion guidance, but the context is clear.

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

Deploy Server