Formatika MCP

Official

by formatika-app

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

video_to-gif

Convert a video fragment to a GIF by setting start, duration, fps, and width. A per-video palette prevents image noise.

Instructions

Video to GIF. Build a GIF from a fragment. The palette is generated for your specific video in a separate pass — without that you get noise instead of a picture. Accepts video/*, .mp4, .mov, .mkv, .webm, .avi, .m4v; up to 500 MB per file.

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": {
      "paths": "<paths>"
    },
    "name": "video_to-gif"
  }
}

Input Schema

Name	Required	Description	Default
`fps`	No	Frames per second. More is smoother and heavier
`from`	No	Start point. 1:30 or 90 both work	0
`paths`	Yes	Paths to the files to process, absolute or relative to the working directory.
`width`	No	Width in pixels. Height follows
`seconds`	No	How many seconds to take
`outputDir`	No	Where to put the results. Defaults to the folder each source file came from. Existing files are never overwritten.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Aug 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the critical palette requirement (separate pass, otherwise noise) and accepted file formats/size limit. No contradictions with structured data.

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 concise sentences front-load the purpose, then add the important palette warning and format constraints. No filler.

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?

The description covers key constraints (formats, size, palette behavior) and the output directory default is in schema. It doesn't elaborate on output naming or failure modes, but for a straightforward converter, it's reasonably complete.

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 covers 100% of parameters, and descriptions in schema are already informative. The tool description doesn't add extra parameter semantics beyond the 'fragment' reference, but baseline 3 is appropriate.

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 the tool builds a GIF from a video fragment, distinguishing it from sibling tools like video_trim or video_convert. It also specifies accepted formats and size limits, reinforcing the scope.

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?

The description implies usage for creating GIFs from video segments, with a note about the palette pass. However, it doesn't explicitly compare with alternatives or state when not to use it, so it's clear context without exclusions.

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