Skip to main content
Glama
LarsCanGit

obs-mcp-server

by LarsCanGit
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

start_streaming

Begin live streaming from OBS Studio to broadcast content to your audience.

Instructions

Start OBS streaming.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • obs-mcp-server.js:416-419 (handler)
    The handler for the 'start_streaming' tool, which calls the OBS 'StartStream' method.
    case "start_streaming": {
  await obs.call("StartStream");
  return ok({ streaming: true });
}
  • obs-mcp-server.js:93-97 (registration)
    The registration of the 'start_streaming' tool with its description and schema.
    {
  name: "start_streaming",
  description: "Start OBS streaming.",
  inputSchema: { type: "object", properties: {} },
},

Tool Definition Quality

C2.7/5.0
Behavior2/5

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

No annotations are provided, yet the description fails to disclose behavioral traits: whether this is idempotent, what happens if already streaming, network requirements, or if it triggers external platform connections. No mention of side effects or return value.

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?

Extremely terse at three words. While not verbose, this level of brevity constitutes under-specification for a state-changing operation rather than effective conciseness. No wasted sentences, but insufficient content.

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 tool initiating external broadcast with no output schema and no annotations, the description is incomplete. It omits success/failure indicators, state management details, and interaction with the streaming lifecycle (toggle behavior).

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

Parameters4/5

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

Input schema has zero parameters. As per scoring rules, 0 parameters equates to a baseline score of 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the basic action (Start) and domain (OBS streaming), but barely escapes tautology by adding 'OBS'. It does not explicitly distinguish from sibling 'start_recording' or clarify streaming scope/destination.

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 provided on when to use this versus 'start_recording', prerequisites (e.g., scene setup), or when to check status first using 'get_status'. No mention of error conditions.

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/LarsCanGit/OBS-MCP'

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