Skip to main content
Glama
Sign In

Shipvo

by io.github.shipvo
OverviewDiscussionsAdmin

record_start

Start recording the phone frame to an MP4 under .shipvo/recordings/. Use record_marker for chapters and record_stop to finish.

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

Input Schema

NameRequiredDescriptionDefault
fpsNoFrames per second (default 30)
lumiNoInclude Lumi and its step captions in the video (default true for recordings; set false for a plain phone).
titleNoUsed in the file name
formatNoVideo shape (default 9:16: 1080x1920; 16:9 is 1920x1080; 1:1 is 1080x1080)
show_tapsNoDraw a finger dot and ripple on taps and a trail on scrolls (default true)
backgroundNoBehind the phone: "brand", "plain" (white) or a CSS colour such as "#102030"
lumi_voiceNoLumi speaks its short step lines with the energetic voice preset (default false). Needs python3, ffmpeg and network access for the voice. Ignored when record_stop gets a narration file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutating-but-non-destructive profile is covered. The description adds the output location and the requirement to call record_stop to finalize the file, which is useful lifecycle context. It does not say whether the call fails when a recording already exists, whether recording runs in the background, or how long the call takes.

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?

Two short sentences with zero filler; the primary action and destination come first, with sibling routing second. Every clause earns its place.

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?

For a recording-start tool with no output schema and a fully documented 7-param schema, the description covers destination, artifact type, and the two follow-up tools. Remaining gaps, such as duplicate-recording behavior and where the result path is surfaced to the agent, are minor.

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 description coverage is 100% with all 7 optional parameters documented, including enums and defaults, so the schema carries the parameter burden. The description adds nothing about parameters such as fps, format, or lumi_voice beyond what is already structured, so the baseline 3 applies.

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?

States a specific verb ('Start recording'), the exact resource ('the phone frame'), the output artifact (MP4) and its destination (.shipvo/recordings/). It also names the two sibling tools it is not (record_marker, record_stop), so an agent can distinguish it from them immediately.

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

Usage Guidelines4/5

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

Explicitly routes the agent: use record_marker for chapters and record_stop to finish, which establishes the start/mark/stop workflow and implies this tool is the entry point. It stops short of stating exclusions, e.g. what happens if a recording is already in progress.

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