Skip to main content
Glama

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

Speaker diarization and labels: transcribe audio with who said what

transcribe_speakers
Read-only

Transcribe a meeting, interview, call or podcast with speaker labels: each turn says which speaker talked, with start and end times (Deepgram Nova-3). MP3/WAV up to 15 minutes, other formats up to 2 MB, by URL or upload. Optional redaction of personal data (pii), card numbers (pci) or numbers, and subtitles with the speaker in each line. Use for meeting minutes, interview transcripts, call reviews and podcast show notes. Example: url=https://upload.wikimedia.org/wikipedia/commons/7/77/Tofino_pronunciation.mp3. Price $0.10/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_speakers"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL of the recording (MP3/WAV up to 15 minutes; M4A, OGG, WebM or FLAC up to 2 MB); or POST the file itself (raw body, multipart `file` part, or base64 in JSON)
redactNopii (names, addresses, phone numbers and other personal data), pci (card numbers) or numbers: replaced in the transcript
languageNoSpoken language code such as en, es, de or fr (default: detected)
subtitlesNosrt or vtt: also return subtitles, each line starting with its speaker

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, open-world and non-idempotent, but the description adds real value beyond them: the $0.10/call price, the x402 USDC or card-key payment path, and the crucial note that each call is charged so repeats are not free — which explains why idempotentHint is false. It also names the underlying model (Deepgram Nova-3). It does not describe the response payload structure, which is the remaining gap.

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?

The capability statement and constraints are front-loaded, and the pricing/idempotency note is placed last where it belongs. A few clauses merely echo the schema (subtitle per-line speaker, redaction modes) and could be trimmed without losing information.

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 does the work of explaining what comes back (speaker-labelled turns with timestamps, optional subtitles) and covers cost, auth and input limits. What remains underspecified is the response envelope itself — e.g. whether the transcript is plain text or structured JSON with a segment array.

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 every parameter (url, redact, language, subtitles) is already fully documented in the schema. The description restates the redaction modes and subtitle behaviour rather than adding format or edge-case detail, so the baseline 3 applies; the only small bonus is a working example URL.

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 a meeting, interview, call or podcast') and immediately names the differentiator: speaker labels with per-turn speaker identity and start/end times. Against siblings like transcribe, audio_transcribe and transcribe_long, the diarization framing is enough for an agent to pick this one without opening a schema.

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?

Concrete use cases are given ('meeting minutes, interview transcripts, call reviews and podcast show notes'), plus the input constraints (MP3/WAV up to 15 minutes, other formats up to 2 MB). There is no explicit exclusion or named alternative for long audio (e.g. transcribe_long for >15 minutes), so the agent must infer that boundary.

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.