Skip to main content
Glama

Fattly

by io.github.industriesfatty-spec
OverviewDiscussionsAdmin

fattly_edit_video

Draw-to-Edit: edits a REGION of a video using a mask + a text instruction (e.g. "make the car burn", "remove the person", "replace with a red car"). The masked area (WHITE on the mask, BLACK elsewhere) is regenerated across the whole clip, the rest is kept. Upload the source video with fattly_upload_media and the mask with fattly_upload_image (other links are rejected). Takes a few minutes; returns the mp4 link, or a generation id to check with fattly_video_status.

Input Schema

NameRequiredDescriptionDefault
promptYesWhat should happen to the masked area.
consentYesMust be true. By setting it you confirm that you have the rights to, and the consent of, every person who is visible or audible in the materials you provide.
maskUrlYesMask image, fal URL. WHITE = area to edit, BLACK = keep unchanged.
videoUrlYesSource video — the URL returned by fattly_upload_media (kind video).
resolutionNoOutput resolution (default 720p).
durationSecondsNoClip length in seconds, 2-12 (default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / videoUrl / description
      Previous value: -"Source video, fal URL (from fattly_upload_image)."New value: +"Source video — the URL returned by fattly_upload_media (kind video)."
  2. Changed2 schema fields changed
    • addedInput schema / properties / consent
      Added value: +{
+  "description": "Must be true. By setting it you confirm that you have the rights to, and the consent of, every person who is visible or audible in the materials you provide.",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "videoUrl",
-  "maskUrl",
-  "prompt"
-]New value: +[
+  "videoUrl",
+  "maskUrl",
+  "prompt",
+  "consent"
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only carry hint flags (readOnly=false, destructive=false, idempotent=false), so the description does real work: it discloses the minutes-long latency, the async return shape (mp4 link or generation id), and that unmasked areas are preserved. It omits cost/credit implications and what happens on failure, keeping it just short of a 5.

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?

Three tight sentences, front-loaded with the mask-and-prompt mechanic, then prerequisites, then latency and return value. No filler and no repeated schema content beyond what aids comprehension.

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

Completeness5/5

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

With no output schema, the description compensates by explaining exactly what is returned (mp4 link or generation id) and how to poll it. Upload constraints and the consent requirement are covered, leaving nothing an agent needs missing before calling.

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%, including the WHITE/BLACK mask convention and the consent statement. The description reinforces the mask semantics and gives prompt examples, but says nothing about resolution or durationSeconds, so it adds little beyond the schema. 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?

Specific verb+resource with scope ('a REGION of a video'), distinguished from sibling tools.

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

Usage Guidelines5/5

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

Explicitly states the prerequisite that the source video must come from fattly_upload_media and the mask from fattly_upload_image, and warns that other links are rejected. It also names the follow-up path (fattly_video_status) for the async case.

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

All Fattly toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources