Skip to main content
Glama
Sign In

Fattly

by io.github.industriesfatty-spec
OverviewDiscussionsAdmin

fattly_animate_photo

Cinema Studio: brings a still photo to life as a video (adds motion). Takes a few minutes. By using this you confirm you have the right to animate the people/content shown.

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": {
      "imageUrl": "<imageUrl>",
      "consent": "<consent>"
    },
    "name": "fattly_animate_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptNoOptional motion/look direction.
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.
modelIdNoVideo model id (default: Cinema model). List: fattly_list_models.
imageUrlYesPhoto to animate — a fal URL from fattly_upload_image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / consent / description
      Previous value: -"Must be true — confirms you have the right to animate the people/content shown."New value: +"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."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations establish it is non-read-only, non-idempotent, non-destructive, and closed-world. The description adds genuine context beyond that: the multi-minute latency and the legal/consent obligation, both relevant behavioral traits for a costly generation call.

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 short sentences, front-loaded with the core transformation, then latency, then the consent caveat. No wasted wording, though it is terse relative to the operation's complexity.

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

Completeness3/5

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

No output schema exists, and the description does not explain what is returned or that this is an async job requiring polling via fattly_video_status – a notable omission for a minutes-long video generation. Latency and consent are covered, but the return/lifecycle pattern is missing.

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 all four parameters are already documented, including consent and the modelId/upload references. The description adds no format or syntax detail beyond the schema, so baseline 3 is appropriate.

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?

The description states a concrete verb and transformation: 'brings a still photo to life as a video (adds motion)', which is specific and distinguishable from generic video generation. It does not explicitly name a sibling (e.g. fattly_generate_video) to draw the boundary, but the input+transformation is clear.

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 – animate a still photo – and it warns the process takes minutes plus requires rights confirmation. However, it gives no explicit when-to-use vs alternatives such as fattly_generate_video or fattly_trend_video, leaving the routing decision to inference.

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