Skip to main content
Glama

Fattly

by io.github.industriesfatty-spec
OverviewDiscussionsAdmin

fattly_generate_video

Generates an AI video from a prompt (or from an image). Takes a few minutes — the tool waits up to ~2 minutes and returns a link to the mp4 file; if it is still rendering, it returns a generation id to check with fattly_video_status.

Input Schema

NameRequiredDescriptionDefault
modelNokling-3-standard | gemini-omni-flash | seedance-2-5 (default kling-3-standard). Full list: fattly_list_models.
promptYesDescription of the video scene.
consentNoREQUIRED (true) whenever you pass inputImageUrl or referenceImageUrls — animating a photo of a real person needs their consent. 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.
durationNoClip length in seconds (model dependent).
aspectRatioNoAspect ratio: 16:9, 9:16 or 1:1 (default 16:9). gemini-omni-flash supports 16:9 and 9:16 only.
inputImageUrlNoOptional start image for image-to-video — must be a fal URL. Get one with fattly_upload_image.
referenceImageUrlsNoOptional MULTIPLE reference images (fal URLs, 2-50) for reference-to-video models like seedance-2-5 — the model blends them into one video. With a single URL the video starts from that image (image-to-video). Get each URL with fattly_upload_image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / aspectRatio / description
      Previous value: -"Aspect ratio, e.g. 16:9, 9:16, 1:1 (default 16:9)."New value: +"Aspect ratio: 16:9, 9:16 or 1:1 (default 16:9). gemini-omni-flash supports 16:9 and 9:16 only."
  2. Changed1 schema field changed
    • changedInput schema / properties / model / description
      Previous value: -"kling-3-standard | veo-3-1 | seedance-2-5 (default kling-3-standard)."New value: +"kling-3-standard | gemini-omni-flash | seedance-2-5 (default kling-3-standard). Full list: fattly_list_models."
  3. Changed1 schema field changed
    • addedInput schema / properties / consent
      Added value: +{
+  "description": "REQUIRED (true) whenever you pass inputImageUrl or referenceImageUrls — animating a photo of a real person needs their consent. 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"
+}
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag it as a non-read-only, non-idempotent write with no destruction, but the description adds behavior the annotations cannot express: the ~2 minute server-side wait, the possibility of an incomplete render, and the two possible return shapes. It stops short of mentioning credit cost or failure modes.

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 clauses, front-loaded with the core action, followed by timing and the fallback path. No filler sentences.

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?

With no output schema, the description correctly carries the return-value burden by explaining the mp4 link vs. generation id outcomes. Combined with the fully documented input schema, an agent has nearly everything needed, though cost and failure behavior are unstated.

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%, so the model, consent, duration, aspect ratio and image parameters are already well documented in structured data. The description only restates the prompt/image duality and adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 and resource ("Generates an AI video") and broadens the input mode to prompt-or-image. It is clear against generic siblings, but it does not differentiate from close video-producing siblings such as fattly_animate_photo, fattly_generate_ad_video or fattly_trend_video.

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?

Gives concrete operational context: the call takes a few minutes and the tool waits ~2 minutes before handing back a generation id. It names the follow-up tool (fattly_video_status) and the polling condition, which is genuine usage guidance, though no explicit when-to-prefer-this-over-sibling rules.

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