Set the output directory where OBS Studio writes recording files, so new recordings are saved to a chosen folder.
Sets the current directory that the record output writes files to
| Name | Required | Description | Default |
|---|---|---|---|
| recordDirectory | Yes | Output directory |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation operation ('Sets'), but fails to specify permissions required, whether changes are persistent, potential side effects, or error conditions. This leaves significant gaps in understanding the tool's behavior beyond its basic function.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, clear sentence that efficiently conveys the tool's purpose without unnecessary words. It is front-loaded with the core action and target, making it easy to parse and understand quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with no annotations and no output schema, the description is inadequate. It lacks details on behavioral traits, usage context, and expected outcomes, leaving the agent with insufficient information to invoke the tool correctly in complex scenarios.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, with 'recordDirectory' documented as 'Output directory'. The description adds no additional parameter details beyond what the schema provides, such as format examples or constraints. Thus, it meets the baseline for high schema coverage without compensating with extra insights.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Sets') and the target ('current directory that the record output writes files to'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'obs-get-record-directory' or 'obs-set-current-profile', which handle related but distinct operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, such as 'obs-get-record-directory' for retrieving the current directory or other 'obs-set-' tools for different settings. The description lacks context on prerequisites or exclusions, offering only basic functional information.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.