Skip to main content
Glama

Transcribe audio

audio_transcribe

Transcribes an audio file at a public https URL on EdgeCloud and returns the text. Charges credits per audio minute, only on success; price it with quote. Needs sign-in (auth_challenge then auth_verify).

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>",
      "minutes": "<minutes>"
    },
    "name": "audio_transcribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
minutesYesAudio length in whole minutes for pricing, 1-30
quote_idNoThe quote_id returned by quote (valid 5 minutes, single use). Use instead of max_price_credits
audio_urlYesPublic https link to the audio file
max_price_creditsNoThe most you'll pay for this call, in Wave credits. Needed unless you pass quote_id; the call fails if the price is higher

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / audio_url / description
      Added value: +"Public https link to the audio file"
    • addedInput schema / properties / audio_url / pattern
      Added value: +"^https://"
    • changedInput schema / properties / max_price_credits / description
      Previous value: -"The most you'll pay, in credits"New value: +"The most you'll pay for this call, in Wave credits. Needed unless you pass quote_id; the call fails if the price is higher"
    • addedInput schema / properties / max_price_credits / minimum
      Added value: +0
    • addedInput schema / properties / minutes / description
      Added value: +"Audio length in whole minutes for pricing, 1-30"
    • addedInput schema / properties / minutes / minimum
      Added value: +1
    • addedInput schema / properties / quote_id / description
      Added value: +"The quote_id returned by quote (valid 5 minutes, single use). Use instead of max_price_credits"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already say this is a non-readonly, non-idempotent, open-world call, so the description doesn't need to rehearse that. It adds information the annotations can't express: billing is per audio minute and is charged only on success, and there is an auth prerequisite chain. It doesn't mention supported formats, size or duration limits, or latency expectations.

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 tight sentences, front-loaded with the action and scope, then pricing and auth. Every clause carries an operational fact; nothing is padding.

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?

With no output schema, the description's 'returns the text' correctly covers the return value, and it covers cost, auth, and quoting. Remaining gaps are minor: supported audio formats, failure behavior on price mismatch (only in schema), and what happens if the actual duration differs from the supplied minutes.

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%, with per-parameter docs for minutes, quote_id, audio_url, and max_price_credits. The description reinforces the pricing model ('per audio minute') and points to quote, but it adds no syntax or format detail beyond the schema, which is the correct baseline.

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 names a specific verb and resource ('Transcribes an audio file') and narrows the scope (public https URL on EdgeCloud), and it states the return ('returns the text'). It doesn't need to distinguish itself from any sibling because the catalog has no competing transcription tool, but it also makes no explicit sibling comparison.

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 concrete prerequisites: sign in via auth_challenge then auth_verify, and get a price via quote. This is real when/how-to guidance for the prerequisite chain, though it states no when-not-to-use conditions or failure recovery beyond what the schema implies.

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.

Resources