Skip to main content
Glama
Sign In

Shipvo

by io.github.shipvo
OverviewDiscussionsAdmin

record_stop

Stop the recording and write the MP4. Returns the file, duration in seconds, size and chapters. With music: true, mixes a ducked music bed under the video and writes a credits JSON next to it (credit the track where you publish).

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": "record_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
musicNoMix a music bed under the video (default false). Needs python3, ffmpeg and ffprobe; picks a track from Jamendo unless SHIPVO_MUSIC_FILE is set.
narrationNoPath to a wav with a voice track. It is mixed over the video, trimmed to the video length (the result says so), and ducks the music when music is true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations only declare non-read-only and non-destructive. The description adds real value beyond them: it writes an MP4, returns file/duration/size/chapters, and with music also writes a credits JSON side file plus a licensing obligation. It still omits what happens on errors or whether an existing file is overwritten.

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 compact sentences, front-loaded with the primary action and return values, then the conditional music branch. No filler, though it is dense enough that the licensing note is easy to miss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description summarizes the return values (file, duration, size, chapters), which is what an agent needs. The narration mixing path goes unmentioned, and preconditions for calling (an active recording) are left implicit.

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 100%, so both parameters are already documented including the ffmpeg/ffprobe and Jamendo dependency details. The description adds the credits-JSON side effect and the 'credit the track' obligation for music, but says nothing about the narration parameter. Baseline 3 fits.

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?

Specific verb+resource: 'Stop the recording and write the MP4,' which clearly complements the sibling record_start. It does not explicitly name the sibling it pairs with, so differentiation is implied by the shared 'record_' prefix rather than stated.

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 by 'Stop the recording' — an agent can infer it follows record_start — and the music branch is given a condition. There is no explicit statement of when not to call it, what happens if no recording is active, or how it relates to record_marker.

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

All Shipvo toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources