Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

run_video_chunk

Read-only

Reads a bounded, base64-encoded chunk of a completed camera recording by job ID and camera, enabling agents to retrieve video output in manageable segments.

Instructions

Read a bounded, base64-encoded chunk of a completed camera recording.

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": {
      "job_id": "<job_id>",
      "camera": "<camera>"
    },
    "name": "run_video_chunk"
  }
}

Input Schema

NameRequiredDescriptionDefault
cameraYes
job_idYes
lengthNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description nonetheless adds real value beyond them: the target must be a *completed* recording (a precondition), the payload comes back base64-encoded (important because there is no output schema), and reads are bounded. It does not describe end-of-stream behavior or a maximum chunk size.

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?

A single front-loaded sentence with no filler, and the scoping qualifiers (bounded, base64, completed) come before the resource noun. It is efficient, though the extreme terseness is part of why parameter meaning is missing.

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 four-parameter, output-schema-less read tool with zero schema descriptions, the definition is too thin: chunk-window semantics, EOF signaling, and size limits are all unaddressed, so an agent must guess how to paginate through a recording.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and largely fails: it never explains that offset and length are the chunk window, what units they use, or what camera and job_id must reference. "Bounded" and "chunk" only vaguely gesture at length and offset, leaving half the parameters undocumented everywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Read") and a precisely scoped resource ("a bounded, base64-encoded chunk of a completed camera recording"), which lets an agent tell this apart from a whole-file export or an inspection tool. It stops short of naming the sibling it complements, so differentiation is good but not explicit.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives such as video_export or video_inspect. The word "completed" implies a job must be finished first, and "chunk" hints at iterative reading, but neither is spelled out as guidance.

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