Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

video_export

Export edited segments from real simulation recordings by specifying run directory, camera, and sim time range, preserving native cadence and saving source hashes.

Instructions

Edit intact real run recordings. Segments require run_directory,camera,start_sim_time_s,end_sim_time_s; optional speed,title. Preserve native cadence, save source hashes and sim/output time mapping. Upscaling requires explicit opt-in.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "segments": "<segments>",
      "destination": "<destination>"
    },
    "name": "video_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputNo
segmentsYes
font_fileNo
destinationYes
allow_upscaleNo
output_resolutionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real behavioral detail beyond the schema: native cadence is preserved, source hashes and sim/output time mappings are recorded, and upscaling is gated behind an explicit flag. However, it omits core write behavior such as where the destination file is written, whether existing files are overwritten, and what the call returns.

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?

Three dense sentences with no filler, and the segment requirements are front-loaded before the secondary behavioral notes. The telegraphic, fragment-style phrasing occasionally costs clarity (the subject of 'Edit' is unclear), but every sentence carries information.

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 six-parameter, unannotated mutation tool with no output schema and no schema descriptions, the definition leaves too much undefined: the destination/output relationship, resolution handling, and font_file are all unaddressed. It covers the nested segment contract well but is not a sufficient basis for invoking the tool correctly end to end.

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?

Schema coverage is 0% across six top-level parameters, so the description must compensate. It does document the segment object's expected keys (run_directory, camera, start_sim_time_s, end_sim_time_s, speed, title), which is valuable since segment items are untyped additionalProperties objects, but destination, output, font_file, and output_resolution remain entirely unexplained.

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 opens with 'Edit intact real run recordings,' which loosely identifies the resource (run recordings) but the verb 'Edit' does not convey that this produces an exported video file; the tool name says export but the prose never does. It distinguishes itself from video_inspect/run_video_chunk only implicitly through mention of segments and destination-bound output.

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?

Usage is implied rather than stated: 'intact real run recordings' narrows the input domain, and 'Upscaling requires explicit opt-in' gives a concrete constraint on one option. There is no explicit when-to-use/when-not guidance and no named alternative (e.g., scene_export or run_video_chunk) to help an agent choose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.