Skip to main content
Glama
yshk-mrt

Presentation Buddy MCP Server

by yshk-mrt

SetLutFilter

Adjust LUT filter parameters like blending amount and file path for video sources in OBS Studio. Modify color grading settings during live streams or recordings.

Instructions

Sets parameters for a LUT filter on a source. 用途: LUTフィルターの適用量やファイルパスをリアルタイムで変更する

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Implementation Reference

  • The handler implementation for the 'SetLutFilter' tool. It extracts parameters (sourceName, filterName, amount, path), constructs filter settings, and calls the OBS WebSocket 'SetSourceFilterSettings' request to update the LUT filter on the specified source.
    case "SetLutFilter":
        console.log(`Executing SetLutFilter with params:`, JSON.stringify(params, null, 2));
        try {
            // Parse the input parameters
            // Check if params are directly in params or in a nested params object
            const paramsObj = params.params || params;
            const sourceName = paramsObj.sourceName;
            const filterName = paramsObj.filterName;
            const amount = paramsObj.amount;
            const path = paramsObj.path;
            
            console.log(`SetLutFilter: Parsed parameters - sourceName: "${sourceName}", filterName: "${filterName}", amount: ${amount}, path: ${path || "undefined"}`);
            
            if (!sourceName || !filterName) {
                throw new Error("Missing required parameters: sourceName or filterName");
            }
            
            console.log(`SetLutFilter: Setting LUT filter "${filterName}" on source "${sourceName}"`);
            
            // Direct approach - skip getting current settings
            console.log("Using direct filter update approach");
            
            const filterSettings: Record<string, any> = {};
            
            if (amount !== undefined) {
                filterSettings.amount = amount;
            }
            
            if (path) {
                filterSettings.path = path;
            }
            
            console.log(`Filter settings to apply:`, JSON.stringify(filterSettings, null, 2));
            
            const setFilterResponse = await sendToObs(
                "SetSourceFilterSettings", 
                {
                    sourceName: sourceName,
                    filterName: filterName,
                    filterSettings: filterSettings
                },
                context,
                action.name
            );
            
            console.log(`SetSourceFilterSettings response:`, JSON.stringify(setFilterResponse, null, 2));
            console.log(`Successfully updated LUT filter settings directly for ${filterName} on ${sourceName}`);
            return { structuredContent: { success: true } };
        } catch (e: any) {
            console.error(`Error in SetLutFilter for OBS:`, e.message);
            console.error(`Error details:`, e);
            return { structuredContent: { success: false, error: e.message } };
        }
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. It mentions real-time changes ('リアルタイムで変更する') which is useful behavioral context, but doesn't disclose critical traits like whether this is a mutation (implied by 'Sets'), permission requirements, error conditions, or side effects. For a tool with 4 nested parameters and no annotation coverage, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief but front-loaded with the core purpose. However, the bilingual format (English/Japanese) adds redundancy without significant benefit, and the second sentence could be integrated more efficiently. It's not overly verbose but could be more structured.

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?

Given the tool's complexity (4 nested parameters, mutation operation, no annotations, no output schema), the description is incomplete. It lacks details on parameter semantics, behavioral expectations, error handling, and output format. The real-time change hint is helpful but insufficient for a tool with this level of complexity.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It only vaguely mentions 'LUTフィルターの適用量やファイルパス' (amount and file path) without explaining all 4 parameters (sourceName, filterName, amount, path) or their relationships. The description adds minimal value beyond the schema's property names.

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 tool's purpose: 'Sets parameters for a LUT filter on a source' with the specific verb 'Sets' and resource 'LUT filter'. It distinguishes from siblings like SetShaderFilter by specifying LUT filters. The Japanese text adds context but doesn't change the core clarity.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites (e.g., needing an existing source/filter), exclusions, or compare to similar tools like SetShaderFilter. Usage is implied through the action but not explicitly defined.

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