Skip to main content
Glama
extentos

extentos

setSimVideo

Set a test video as the simulator's camera source so capture_photo, capture_video, and videoFrames run against a known scene, enabling reliable testing of camera-driven flows.

Instructions

Pipe a Test Video into the simulator's camera input so capture_photo / capture_video / videoFrames run against a known scene instead of a blank viewport — closes the agent-driven test loop for camera-driven flows the same way injectTranscript closes it for voice flows. Discover available IDs via getSimulatorStatus.testVideos (bundled defaults + project uploads). Requires the simulator browser tab to be connected (browser role attached) — call ensureSimulatorBrowser({ sessionId }) first to guarantee it (idempotent: opens the tab cross-platform + polls until it attaches). Same precondition as the simulator's photo/video capture itself. The browser loads the video as its cameraSource (same code path as a human drag-dropping a file), and a camera_source_set lifecycle event lands in getEventLog so the source change is visible to your verification step. USE before triggering a capture_photo / capture_video flow that needs a scene. DON'T USE to upload new videos — that's the project simulator page's job (extentos.com/projects//simulator).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
videoIdYesID of the test video to load. Get the available list from getSimulatorStatus.testVideos — each entry has an id, name, description, durationSec, and source ('default' = bundled, 'project' = uploaded via the simulator page).
sessionIdYes
Behavior5/5

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

No annotations provided, but description fully discloses behavior: loads video as cameraSource, same code path as drag-drop, emits lifecycle event, requires browser role attached, and is idempotent with ensureSimulatorBrowser.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, all sentences add value, but could be slightly more concise; still well-structured.

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 no annotations and no output schema, the description provides complete context: purpose, prerequisites, discovery method, when/not to use, and relation to other tools.

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?

Adds meaning for videoId (where to get it, fields) beyond schema, but sessionId parameter lacks description in both schema and description, despite being required.

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 it pipes a test video into the simulator's camera input so capture_photo/capture_video/videoFrames use a known scene, distinguishing it from siblings like injectTranscript.

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

Usage Guidelines5/5

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

Explicitly says 'USE before triggering a capture_photo/capture_video flow that needs a scene' and 'DON'T USE to upload new videos', plus describes prerequisite of browser tab connection and suggests ensureSimulatorBrowser.

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/extentos/mcp-server'

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