Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Get Input Default Settings

obs-get-input-default-settings
Read-onlyIdempotent

Retrieve default settings for a specified input kind in OBS Studio, providing a baseline configuration to streamline source setup and customization.

Instructions

Gets the default settings for an input 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": {
      "inputKind": "<inputKind>"
    },
    "name": "obs-get-input-default-settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputKindYesInput kind to get the default settings for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint false, idempotentHint, and destructiveHint false, so the safety profile is well covered. The description adds no extra behavioral context like return shape or error behavior, but it does not contradict the annotations.

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 short sentence with the verb and object front-loaded. Every word earns its place, and there is no redundant repetition of schema or annotations.

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?

The tool is simple and the annotations plus schema cover safety and the parameter adequately. However, the lack of usage alternatives and the absence of an output schema mean the description does not convey what the returned default settings look like or how to obtain valid inputKind values.

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?

Schema description coverage is 100%, and the single inputKind parameter is fully described in the schema. The description merely restates 'input kind' without adding examples, allowed values, or format details, so it meets the schema baseline but does not exceed it.

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?

The description clearly states the action ('Gets') and the resource ('default settings for an input kind'). The phrase 'default settings' and 'input kind' distinguishes it from related siblings like obs-get-input-settings and obs-get-filter-default-settings.

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 guidance is provided about when to use this tool versus alternatives, such as when current input settings are needed instead of defaults. It also does not mention discovering valid input kinds via obs-get-input-kind-list.

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