Skip to main content
Glama
Sign In

Fattly

by io.github.industriesfatty-spec
OverviewDiscussionsAdmin

fattly_transcribe

Transcribes an audio file to text with timed segments. Returns the transcript as JSON.

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": {
      "audioUrl": "<audioUrl>"
    },
    "name": "fattly_transcribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNotranscribe (default) or translate to English.
audioUrlYesAudio to transcribe — the URL returned by fattly_upload_media (kind audio).
languageNoLanguage hint, e.g. en, pl (auto-detect if omitted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / audioUrl / description
      Previous value: -"Audio to transcribe — a fal URL from fattly_upload_image (kind audio)."New value: +"Audio to transcribe — the URL returned by fattly_upload_media (kind audio)."
  2. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations declare this is a non-read-only, non-idempotent, non-destructive call, so the agent knows it is a mutating/consuming operation. The description adds almost nothing beyond that: it doesn't mention credit consumption, processing time, length limits, or language auto-detect behavior — all relevant for a paid transcription call.

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 short sentences, front-loaded with the action, no filler. Every clause carries information.

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?

There is no output schema, and 'returns the transcript as JSON' does not describe the shape (segment fields, timestamps, text). Given no output schema exists, some return-value detail would have been valuable; coverage is adequate but incomplete for an agent that needs to consume the result.

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 (task enum, audioUrl, language) are already documented in the schema, including the translate-vs-transcribe choice and auto-detect fallback. The description adds no parameter-level detail, 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 ('Transcribes an audio file to text') plus an output characteristic ('with timed segments'). It distinguishes itself reasonably from generation siblings like generate_audio or clone_voice, but does not explicitly position itself against any sibling.

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

Usage Guidelines2/5

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

No guidance on when to use this versus other tools, no mention of prerequisites (an uploaded audio asset), and no note on cost or async behavior. The only hint about upstream usage lives in the schema's audioUrl description, not the tool description.

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