Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Stop Virtual Camera

obs-stop-virtual-cam
Idempotent

Stop the active virtual camera output in OBS Studio. Use this tool when you need to end virtual cam streaming and release the camera feed.

Instructions

Stops the virtualcam output

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "obs-stop-virtual-cam"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=false (write operation), destructiveHint=false (non-destructive), and idempotentHint=true. The description adds no extra behavioral context beyond restating the action. While it does not contradict annotations, it does not enhance them either, so it meets the baseline for a trivial tool.

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, direct sentence with no unnecessary words. It front-loads the core purpose and contains only the essential information. This is ideal conciseness, though it is minimal.

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

Completeness5/5

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

For a tool with no parameters and no output schema, the description fully covers what the tool does. Annotations provide the safety profile (idempotent, non-destructive). The context is simple enough that no further elaboration is needed, making the description complete.

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?

There are zero parameters, so schema coverage is 100% by default. The description does not need to explain parameters, and the baseline for 0 parameters is 4. The description adds no additional information, but that is acceptable given there is nothing to document.

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 'Stops the virtualcam output' uses a specific verb ('stops') and resource ('virtualcam output'), clearly identifying the action. It is distinct from sibling tools like obs-start-virtual-cam and obs-toggle-virtual-cam, which handle start and toggle operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool (to stop the virtual camera) but does not explicitly mention alternatives or exclusions, such as noting that 'obs-toggle-virtual-cam' could be used interchangeably or that stopping is idempotent. With no explicit guidance, it is adequate but not strong.

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