Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

OBS Sleep

obs-sleep
Read-onlyIdempotent

Sleep for a specified number of milliseconds or frames.

Instructions

Sleeps for a time duration or number of frames

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-sleep"
  }
}

Input Schema

NameRequiredDescriptionDefault
sleepFramesNoNumber of frames to sleep for
sleepMillisNoNumber of milliseconds to sleep for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and idempotentHint=true, so the safe, non-mutating nature is established. The description adds that it can sleep by milliseconds or frames, giving concrete behavioral specifics beyond 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?

One short, clear sentence with no redundancy; all words earn their place.

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?

Given the tool's simplicity, two optional parameters, solid schema descriptions, and annotations, this description is adequate. It explains the core behavior without needing to detail return values (none) or complex side effects.

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?

Both parameters are fully described in the schema (100% coverage), so the description doesn't need to add much. It does align the two units ('time duration' = sleepMillis, 'number of frames' = sleepFrames), but it doesn't clarify precedence or exclusivity, so it adds minimal value over the schema.

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 uses the verb 'sleeps' and specifies the resource ('a time duration or number of frames'), making it clear this is a wait/timing tool. It is distinct from the 150+ OBS sibling tools, none of which perform timing delays.

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 states what the tool does but gives no context for when to use it relative to alternatives, such as 'use this to insert a delay between OBS operations.' Since there are no sibling sleep tools, it is not actively misleading, but it lacks explicit usage guidance.

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