Skip to main content
Glama
takurot
by takurot

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
start_showC

Start a show and execute opening sequence. Loads show template and initializes state.

end_showB

End the current show. Optionally play ending sequence and stop streaming/recording.

switch_segmentC

Switch to a different segment of the show.

extend_segmentC

Extend the current segment's timer.

get_current_show_stateB

Get the current show state including segments, overlays, and timers.

get_obs_healthA

Get OBS connection status and health metrics.

set_safety_modeC

Set the safety mode (strict, normal, debug).

get_debug_configB

Get masked configuration for debugging connection issues.

reconnect_obsA

Try to reconnect to OBS WebSocket using current configuration.

set_audio_moodC

Set the audio mood profile.

trigger_effectC

Trigger a visual effect.

show_overlayC

Show an overlay.

hide_overlayD

Hide an overlay.

take_stream_snapshotC

Take a snapshot of the current stream.

update_source_contentC

Update the content of an OBS source.

mark_highlightC

Mark a highlight point in the stream.

get_scene_listB

Get list of available scenes.

set_sceneC

Switch the current program scene.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Current Show StateCurrent show state including segment, overlays, and timers

TDQS

B3/5.0

Scored across 18 tools

Disambiguation4/5

Most tools are clearly distinct by resource and action: start_show/end_show/switch_segment handle show flow, while set_scene/get_scene_list handle scenes, and show_overlay/hide_overlay handle overlays. The only mild ambiguity is between switch_segment and set_scene, and between trigger_effect and update_source_content, but the descriptions clarify their different purposes. Overall boundaries are distinct.

Naming Consistency5/5

The naming is highly consistent: nearly all tools use a clear verb_noun pattern (start_show, end_show, switch_segment, show_overlay, hide_overlay, get_scene_list, set_scene). All use snake_case with imperative verbs. The style is uniform and predictable throughout.

Tool Count4/5

18 tools for a show-runner MCP server feels appropriate given the breadth of capabilities it needs to cover: show lifecycle, OBS scene management, overlays, effects, health monitoring, and audio. Each tool serves a distinct function and none feel extraneous for the apparent scope of running live shows via OBS.

Completeness4/5

The tool set covers show lifecycle (start/end/segment), OBS scene control, overlays, audio, effects, and health/connection diagnostics. Gaps exist: no segment rollback or scene visibility controls, and no realtime state subscription mechanism, but the core show-running operations and OBS basics are covered. The inclusion of debugging utilities (get_debug_config, reconnect_obs) is a thoughtful addition, though there's no explicit 'stop' for effects or a way to revert sources.

Maintenance

ActivityInactive
ResponsivenessNo issues