Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Get Filter Default Settings

obs-get-filter-default-settings
Read-onlyIdempotent

Get default settings for any OBS filter kind. Retrieve initial configuration values to apply or customize filters in OBS Studio.

Instructions

Gets the default settings for a filter kind

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": {
      "filterKind": "<filterKind>"
    },
    "name": "obs-get-filter-default-settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterKindYesFilter kind to get the default settings for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description does not add behavioral context beyond confirming a read operation; it omits details like return format, error conditions, or side effects. Since it adds no extra value over annotations, the score is low.

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

Conciseness5/5

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

The description is a single, clear, and front-loaded sentence with no wasted words. It efficiently communicates the tool's purpose.

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

Completeness3/5

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

For a simple one-parameter getter with read-only and idempotent annotations, the description is adequate but does not explain what 'default settings' entails or what the response contains. Given the absence of an output schema, a bit more detail would help, but the simplicity keeps it at an acceptable level.

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 schema fully describes the only parameter (filterKind) with 100% coverage. The description does not add parameter-specific information beyond the general purpose, so the baseline score of 3 applies.

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: to get default settings for a filter kind. It uses a specific verb ('Gets') and resource ('default settings for a filter kind'), distinguishing it from input-related siblings by specifying 'filter kind'. However, it doesn't explicitly differentiate from similar tools like obs-get-input-default-settings, so a slight deduction.

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, nor does it mention prerequisites or related tools. It only states the action without any contextual usage hints.

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