Skip to main content
Glama
deenesjakoruzh
yshk-mrt

Presentation Buddy MCP Server

by yshk-mrt
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

TriggerStudioModeTransition

Switch from Preview to Program in Studio Mode to manage scene transitions during live streaming or recording sessions.

Instructions

Triggers the transition from Preview to Program in Studio Mode. 用途: シーンの準備と切り替えをスムーズに行う

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Implementation Reference

  • src/index.ts:733-741 (handler)
    The handler implementation for the 'TriggerStudioModeTransition' MCP tool. It logs the execution, sends an OBS WebSocket request named 'TriggerStudioModeTransition' with empty parameters via sendToObs, and returns success or error structured content.
    case "TriggerStudioModeTransition":
    console.log(`Executing TriggerStudioModeTransition`);
    try {
        await sendToObs("TriggerStudioModeTransition", {}, context, action.name);
        return { structuredContent: { success: true } };
    } catch (e: any) {
        console.error(`Error in TriggerStudioModeTransition for OBS:`, e.message);
        return { structuredContent: { success: false, error: e.message } };
    }

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Triggers the transition' implies a state-changing action, the description doesn't specify whether this requires specific conditions (like being in Studio Mode), what happens if triggered incorrectly, whether it's reversible, or what side effects might occur. The Japanese text adds no behavioral information.

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 reasonably concise with two brief sentences. However, the Japanese text ('用途: シーンの準備と切り替えをスムーズに行う') is redundant with the English portion and adds no new information, slightly reducing efficiency. The core purpose is front-loaded effectively.

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

Completeness2/5

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

For a state transition tool with no annotations, no output schema, and minimal parameter documentation, the description is insufficient. It doesn't explain what happens after triggering the transition, what errors might occur, or how this integrates with the broader OBS workflow represented by sibling tools. The Japanese translation doesn't add meaningful context.

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 shows one required parameter 'params' with an empty properties object (0% schema description coverage). The description provides no information about what 'params' should contain or how it affects the transition. With no parameter guidance in either schema or description, this meets the baseline for minimal documentation.

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 clearly states the action ('Triggers the transition') and the specific resource ('from Preview to Program in Studio Mode'), making the purpose understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'SwitchScene' or 'SetTransitionSettings', which might have overlapping functionality in scene management contexts.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'SwitchScene' and 'SetTransitionSettings' available, there's no indication of when this specific transition trigger is appropriate, what prerequisites exist, or when other tools should be used instead.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yshk-mrt/obs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server