Skip to main content
Glama

Fattly

by io.github.industriesfatty-spec
OverviewDiscussionsAdmin

fattly_clone_voice

Voice: either clone a NEW voice from a sample and speak text with it, or REUSE a saved voice (cheaper). Use only voices you have the right to use.

Input Schema

NameRequiredDescriptionDefault
textYesWhat the voice should say.
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. For a voice: it is your own voice or you have the speaker's consent.
voiceIdNoId of a voice you saved earlier — reuse it instead of cloning (cheaper).
saveNameNoIf set when cloning, saves the voice under this name for reuse.
sampleUrlNoVoice sample to clone — the URL returned by fattly_upload_media (kind audio). Required when cloning a new voice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sampleUrl / description
      Previous value: -"Voice sample to clone — a fal URL. Required when cloning a new voice."New value: +"Voice sample to clone — the URL returned by fattly_upload_media (kind audio). Required when cloning a new voice."
  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. For a voice: it is your own voice or you have the speaker's consent.",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "text"
-]New value: +[
+  "text",
+  "consent"
+]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare that this is not read-only, not idempotent, not destructive, and closed-world. The description adds useful context about consent/rights and the cheaper reuse path, but does not explain credit usage, failure behavior, or what happens when saveName is used.

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?

The description is two short sentences with no wasted language; the core clone/reuse choice is front-loaded and the legal constraint is concise.

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 five-parameter tool with full schema coverage and annotations, the description is nearly complete: it explains the two operating modes and consent requirement. It could say more about the expected result, but with no output schema this is a minor gap.

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 schema already documents text, consent, voiceId, saveName, and sampleUrl. The description reinforces the sample-vs-saved-voice distinction but adds no syntax or format details beyond the schema.

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 specific action and resource: cloning a new voice from a sample or reusing a saved voice to speak text. It distinguishes the two internal modes, but does not explicitly differentiate this from sibling audio tools such as fattly_generate_audio.

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?

It gives clear mode-selection guidance: clone a NEW voice from a sample, or REUSE a saved voice because it is cheaper. It also adds a legal-use condition, though it does not state when to prefer this tool over sibling tools.

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