Skip to main content
Glama

APEX AI, LLM, Embeddings, OCR & Media

Audio transcribe

audio_transcribe
Read-onlyIdempotent

Transcribe speech from any public audio URL (MP3/WAV/M4A/OGG/WebM/FLAC, max 15 MB) via Whisper Large v3 Turbo with optional timestamps. $0.005 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
urlYespublic http(s) audio URL
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
languageNooptional 2-letter ISO language hint (e.g. en, de)
timestampsNoset 1 to include segment timestamps

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?

Annotations only declare the safety profile (readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false); the description adds the behavior that actually matters for calling correctly — a hard cost of $0.005 per call, the settlement networks and currencies (USDC on Arc/Base/Solana, XNT on X1), the two-phase payment handshake, and the 15 MB input ceiling. These are prerequisites and side effects an agent cannot infer from structured fields.

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?

Three dense sentences, front-loaded with capability and constraints before pricing and the payment procedure. Every clause carries information, though the cryptocurrency/chain enumeration is heavy for a transcription tool and could be compressed to a pointer for payment details.

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 the description never states what comes back — a plain transcript string, an object, or segments when timestamps=1. It also doesn't mention size/latency or error behavior for unsupported URLs. For a paid tool with no output schema, the response shape should have been described.

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 baseline is 3. The description goes beyond the schema by explaining payment as a negotiation loop (obtain terms unsigned, then supply the signed base64 PAYMENT-SIGNATURE payload) and by calling out timestamps as optional, which gives the parameter operational meaning rather than just a type.

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?

The description opens with a specific verb and resource — 'Transcribe speech from any public audio URL' — and immediately qualifies it with accepted formats, a size cap, the underlying model (Whisper Large v3 Turbo), and an optional timestamps feature. That is far more than a restatement of the name, and none of the listed siblings do transcription, so scope is unambiguous.

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?

The description gives explicit procedural guidance for the two-step x402 flow: 'Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`.' That tells an agent exactly how to sequence calls. It does not discuss when-not to use it or any alternative (e.g., local transcription), but with no competing sibling the practical guidance need is met.

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.