Skip to main content
Glama
Sign In

FreeTTS

by org.freetts
OverviewDiscussionsAdmin

Transcribe audio (speech to text)

transcribe_audio
Read-onlyIdempotent

Turn a recording into text with FreeTTS speech to text. Give a public https URL to an audio file (mp3, wav, m4a, ogg, webm). Needs a connected FreeTTS PRO account.

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": {
      "audio_url": "<audio_url>"
    },
    "name": "transcribe_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the recording, like 'en-US', 'de-DE', 'Arabic' or 'es', or 'auto' to detect it (default).
audio_urlYesPublic https URL of the audio file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the description's job is to add context — which it does by disclosing the PRO-account authorization requirement and the public-URL constraint. It stops short of describing latency, size limits, or output format.

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, followed immediately by the input requirement and the account prerequisite. No filler or redundancy.

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 two-parameter, single-purpose tool with annotations covering safety, the essentials (input form, accepted formats, account requirement) are present. There is no output schema, and the description only loosely indicates the return value ('text'), but that is a minor gap for such a simple operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by enumerating accepted audio formats (mp3, wav, m4a, ogg, webm), which the schema does not mention. It adds no detail on the language parameter, so it is not a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Turn a recording into text') and names the provider (FreeTTS speech to text). This is trivially distinguished from the sibling speech-generation tools (text_to_speech, dialogue_to_speech, script_to_tracks) because it is the inverse direction.

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 preconditions: a public https URL and a connected FreeTTS PRO account. It does not name alternatives or state exclusions, but no sibling competes for the same transcription task, so the practical guidance is complete enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FreeTTS 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