Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Speech to text, transcribe audio: Whisper transcription of an audio file

transcribe
Read-only

Transcribe speech from an audio file at a public URL, or uploaded in a POST body, using Whisper large-v3-turbo. Returns the transcript text, detected language, duration and word count; subtitles=srt or vtt adds subtitle text and timestamps=true adds timed segments and words. Accepts common formats such as MP3, WAV, M4A and OGG up to 5 MB, in 90+ languages. Use for voice notes, podcast clips, meeting snippets, subtitles and voice messages. Example: url=https://commons.wikimedia.org/wiki/Special:FilePath/En-us-hello.ogg. Price $0.01/call via x402 USDC or a card key (/credits); failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "url": "<url>"
    },
    "name": "transcribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL of an audio file (max 5 MB); or POST the file itself (raw body, multipart `file` part, or base64 in JSON)
languageNoSpoken language code such as en, sv or de (default: detected)
subtitlesNosrt or vtt: also return subtitle text
timestampsNotrue: also return timed segments and words

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the 5 MB cap, the 90+ language support, the exact returned fields, the cost model ($0.01/call via x402 USDC or card key, failed calls free), and warns that repeat calls are charged. The 'repeats are not free' note usefully reinforces the idempotentHint=false annotation in human terms.

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?

Purpose and model are front-loaded, and the pricing/behavior caveat is placed at the end where it belongs. The single dense paragraph packs a lot in, though the example URL and pricing clause lengthen it slightly more than strictly needed.

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

Completeness5/5

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

For a four-parameter tool with no output schema, the description covers inputs, constraints, return fields, cost, and safety implications. An agent has everything needed to call it correctly on the first attempt.

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 baseline is 3. The description restates what subtitles and timestamps do and adds the public-URL and size constraint, but contributes little syntax or format detail beyond the schema entries.

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 ('Transcribe speech from an audio file') plus the exact model used (Whisper large-v3-turbo) and the accepted input routes (public URL or POST body). An agent can immediately tell this apart from the reverse-direction sibling text_to_speech.

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 use cases — voice notes, podcast clips, meeting snippets, subtitles, voice messages — which is clear context for selection. It stops short of naming when NOT to use it or naming an explicit alternative tool, so it falls just below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.