Skip to main content
Glama

Fattly

by io.github.industriesfatty-spec
OverviewDiscussionsAdmin

fattly_face_swap

Swaps the face from one image onto another. SFW-only and the result is scanned — use only faces you have the right to use; do not create misleading or explicit imagery.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
baseImageUrlYesScene image (the body/photo to keep) — fal URL.
swapImageUrlYesFace image to place into the scene — fal URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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: -[
-  "baseImageUrl",
-  "swapImageUrl"
-]New value: +[
+  "baseImageUrl",
+  "swapImageUrl",
+  "consent"
+]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare the mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), and the description adds genuinely new behavior: the output is scanned and the request is policed for SFW/rights compliance. Disclosing that results are moderated is real behavioral context not present in the structured fields, though the response format itself remains unspecified.

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 sentences, no filler; the core operation comes first and the policy constraints follow. Every clause carries weight.

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 three-parameter mutation with fully documented schema and no output schema, the description covers the operation and its compliance guardrails adequately. Minor gap: nothing about output/result delivery or typical latency for a scanned generation.

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 three parameters (including the consent boolean) are already well documented in the schema. The description adds no syntax, format, or URL-handling detail beyond it, making the baseline 3 correct.

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+resource ('Swaps the face from one image onto another') that is immediately understandable. It does not, however, differentiate itself from a close sibling like fattly_actor_swap, leaving the agent to infer the distinction from names alone.

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?

The description supplies meaningful constraints — SFW-only, rights/consent required, no misleading or explicit imagery — which function as 'when not to use' guidance. It stops short of telling the agent when to prefer this over fattly_actor_swap or other swap/animate siblings, so usage routing is only implied.

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