Skip to main content
Glama

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

Meeting transcript and summary: voice note or meeting recording to summary and action items

transcribe_summary
Read-only

Summarize a voice note, meeting, call or podcast in one call: transcribes up to 60 minutes (MP3/WAV up to 25 MB; M4A, OGG or WebM up to 5 MB) by URL or upload, then returns a title, summary, key points, action items with owner and due date, open questions and the transcript, in the recording's language. Use for meeting notes, voicemail to CRM and call notes. Example: url=https://upload.wikimedia.org/wikipedia/commons/7/77/Tofino_pronunciation.mp3. Price $0.05/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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL of the recording (MP3/WAV up to 25 MB and 60 minutes; M4A, OGG or WebM up to 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)
transcriptNofalse: leave the full transcript out of the answer (default true)

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 already declare readOnlyHint=true and destructiveHint=false, but the description adds real context beyond them: pricing ('$0.05/call via x402 USDC or a card key'), 'failed calls free', and 'each call is charged, so repeats are not free', which explains the non-obvious idempotentHint=false. It also gives concrete input ceilings (60 minutes, 25 MB for MP3/WAV vs 5 MB for M4A/OGG/WebM), which is the failure mode an agent must avoid.

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?

A single dense block, but front-loaded with the core promise and then limits, output shape, use cases, a runnable example URL, and pricing, so each clause carries weight. The main cost is the run-on structure that makes the size limits and the return fields harder to scan than a short bulleted list would be.

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?

With no output schema, the description enumerates the return payload (title, summary, key points, action items with owner and due date, open questions, transcript), and it covers input limits, auth/payment paths, and side-effect profile. An agent has everything needed to decide and to call it correctly.

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 coverage is 100%, so the url, language and transcript parameters are already documented, including the 'default: detected' and 'false: leave the full transcript out' semantics. The description reinforces the format/size limits and notes the output is 'in the recording's language', but adds little that the schema does not already say, so the baseline 3 applies.

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 chain and resource ('Summarize a voice note, meeting, call or podcast in one call: transcribes ... then returns a title, summary, key points, action items ... and the transcript'). It also enumerates the return artifacts, which distinguishes it from plain transcribe_* siblings and from ai_summarize_text in the sibling list without needing to open either 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?

'Use for meeting notes, voicemail to CRM and call notes' gives concrete use contexts, and 'in one call' implies it replaces a transcribe-then-summarize chain. It stops short of naming an exclusion, e.g. directing transcript-only jobs to audio_transcribe or plain summarization of existing text to ai_summarize_text, so it is clear context without explicit alternatives.

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.