Skip to main content
Glama
bdstark

gma3-mcp

by bdstark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Configure a sequence executor's functions

gma3_configure_executor

Configure a grandMA3 sequence executor's key, MA-key, fader, encoder, and Fix functions by page/executor; validates values and leaves playback untouched.

Instructions

Set the key, MA-key, fader and encoder functions and Fix of the sequence executor at Page . by writing its properties (KeyPress, KeyUnpress, MAKeyPress, MAKeyUnpress, Fader, Encoder, EncoderLeft, EncoderRight, Fix; unlike 'Assign At', this never clears the unpress function). The executor must hold a sequence; functions are validated against the sequence lists before anything is sent (keys: Flash, Temp, Swap, Black and Time are key-only). Executor settings belong to this executor only; sequence settings (Wrap Around, priority, ...) are configured with gma3_configure_sequence. lock: true/false sets the executor's own Lock. A page lock also blocks executor changes. Never sends Go, On, Off, Toggle, Flash or any other playback keyword and does not touch the selection, the programmer or fader levels; playback state is read before and after (playback.activeBefore/activeAfter) and configuration alone does not start playback. A locked target is refused before anything is sent (the console silently ignores writes to it) unless unlock: true, which unlocks the owning object, applies the changes and locks it again (relocking is attempted even after a failed change). preview: true performs only the reads and returns the planned changes (from -> to); values already set are reported as unchanged and never sent. Each value is written with one 'set' request whose reply must read back the requested value, because the console silently keeps the previous value for anything it does not accept; the first failure stops the remaining changes. A value that could not be read is unknown, never a default: the call is refused when a value the plan depends on (requested property, Lock, page Lock) is missing, and a set reply without a value is an unknown step. verify (default true) reads every changed property and the lock back. Mutations from this server are serialised, but not isolated from other operators or clients.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fixNoFix the executor on every page (Fix).
lockNoFinal state of the executor's own Lock; lock: false on a locked executor removes the lock (explicit unlock).
pageYesExecutor page number (1-9999); the page must exist.
faderNoFader function: Empty, Master, X, XA, XB, Temp, Rate, Speed, Time (Empty clears it).
unlockNoAllow unlocking a locked executor and/or page for this call; the locks are restored afterwards (default false: refuse).
verifyNoRead the changed properties back and compare (default true).
encoderNoEncoder function: Empty, Master, X, XA, XB, Temp, Rate, Speed, Time (Empty clears it).
previewNoOnly read and report the planned changes (default false).
executorYesExecutor number on that page: 101-190 (keys), 201-290 (faders), 301-390 and 401-490 (knobs), plus the Xkeys 191-198 and 291-298.
key_pressNoKeyPress function: Empty, Go+, Go-, <<<, >>>, On, Off, Toggle, Top, Kill, Pause, Goto, Load, Select, SelectFixtures, Rate1, Speed1, Learn, LearnSpeed, HalfSpeed, DoubleSpeed, ReSync, FastSync, Flash, Temp, Swap, Black, Time (Empty clears it).
key_unpressNoKeyUnpress function: Empty, Go+, Go-, <<<, >>>, On, Off, Toggle, Top, Kill, Pause, Goto, Load, Select, SelectFixtures, Rate1, Speed1, Learn, LearnSpeed, HalfSpeed, DoubleSpeed, ReSync, FastSync (Empty clears it).
encoder_leftNoEncoderLeft function: Empty, Go+, Go-, <<<, >>>, On, Off, Toggle, Top, Kill, Pause, Goto, Load, Select, SelectFixtures, Rate1, Speed1, Learn, LearnSpeed, HalfSpeed, DoubleSpeed, ReSync, FastSync (Empty clears it).
ma_key_pressNoMAKeyPress function: Empty, Go+, Go-, <<<, >>>, On, Off, Toggle, Top, Kill, Pause, Goto, Load, Select, SelectFixtures, Rate1, Speed1, Learn, LearnSpeed, HalfSpeed, DoubleSpeed, ReSync, FastSync, Flash, Temp, Swap, Black, Time (Empty clears it).
encoder_rightNoEncoderRight function: Empty, Go+, Go-, <<<, >>>, On, Off, Toggle, Top, Kill, Pause, Goto, Load, Select, SelectFixtures, Rate1, Speed1, Learn, LearnSpeed, HalfSpeed, DoubleSpeed, ReSync, FastSync (Empty clears it).
ma_key_unpressNoMAKeyUnpress function: Empty, Go+, Go-, <<<, >>>, On, Off, Toggle, Top, Kill, Pause, Goto, Load, Select, SelectFixtures, Rate1, Speed1, Learn, LearnSpeed, HalfSpeed, DoubleSpeed, ReSync, FastSync (Empty clears it).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so richly: it never sends playback keywords, does not touch selection/programmer/fader levels, reads playback state before/after, refuses locked targets unless unlock:true (with re-lock semantics), and details the single 'set'-with-read-back write model, unknown-value handling and verify default true. This is unusually complete disclosure.

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?

Purpose is front-loaded in the first clause, and essentially every sentence conveys a distinct behavioral fact. The prose is dense and clause-heavy, which costs some readability, but there is little wasted text.

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 15-parameter mutation tool with no annotations and no output schema, the description covers prerequisites (executor must hold a sequence), validation, refusal conditions, write/verify semantics, lock interplay and even the read-back state it returns (playback.activeBefore/activeAfter, from -> to plan). Nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: functions are validated against the sequence lists, keys Flash/Temp/Swap/Black/Time are key-only, lock:false explicitly unlocks, and unlock restores locks afterwards. That said, most per-parameter value detail already lives in 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?

States a precise verb and resource: setting KeyPress, MAKeyPress, fader, encoder and Fix functions of the sequence executor at Page <p>.<e> by writing its properties. It also distinguishes itself from nearby siblings by naming gma3_configure_sequence and contrasting with 'Assign <function> At'. An agent can tell what this tool does versus gma3_assign_to_executor and gma3_executor_settings.

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 routes sequence-level settings (Wrap Around, priority) to gma3_configure_sequence and confines executor settings here, notes the executor must hold a sequence, and documents the key-only function restriction. It also states the conditions governing lock/unlock, preview and verify.

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