Skip to main content
Glama
Sign In
@vocea.app/mcp-server

@vocea.app/mcp-server

Official
by vocea-admin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vocea_transcribe

Transcribe base64-encoded audio to text. Supports multiple formats (mp3, wav, ogg, webm, flac) up to 10MB and various languages via BCP-47 codes.

Instructions

Transcribe audio from a base64-encoded string to text (STT).

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_base64": "<audio_base64>"
    },
    "name": "vocea_transcribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
audio_base64YesBase64-encoded audio file (mp3, wav, ogg, webm, flac, max 10MB)
mime_typeNoMIME type, e.g. audio/mpegaudio/mpeg
languageNoBCP-47 language code, e.g. en-US (default: es-ES)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic function and does not mention any limitations, authentication needs, or side effects.

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?

A single sentence that is concise and front-loaded with the core action; no superfluous words.

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?

The description is minimal but covers the main purpose; however, it lacks details about output format, maximum file size (present in schema but not description), and any behavioral context needed for a complete understanding.

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?

The input schema has 100% coverage with descriptions for each parameter, so the description adds no additional meaning beyond the schema. Baseline score of 3 is appropriate.

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 clearly states the verb 'Transcribe' and the resource 'audio from a base64-encoded string to text', and it's distinct from sibling tools like audio generation or listing voices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives; no mention of prerequisites or when not to use it.

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

Deploy Server

Other Tools