Skip to main content
Glama

Sats4AI - Bitcoin-Powered AI Tools

voice_bridge_say

Inject audio into an open Voice Bridge call. Two modes: (1) text — we synthesize speech in any of 602 languages (English, Spanish and German start fastest); (2) audio_base64 + encoding — bring your own audio (mulaw_8000 or pcm_l16_16000 for MVP). Keep each reply to one or two sentences: the call is turn-based. While you speak, the callee cannot interrupt, and what they say is NOT heard (transcription is muted so you do not hear yourself, and for under a second after). One call takes at most 700 speech units of text, about 45 seconds of speech (each Chinese, Japanese, Korean or Thai character counts 3): send a longer message as several calls. The call returns when the speech has finished playing. If it fails after part of the line was spoken, the error says so: do not repeat the start. No additional payment — covered by the session deposit.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "voice_bridge_say"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoText to speak (mode 1). One or two sentences work best; at most 700 speech units (each Chinese, Japanese, Korean or Thai character counts 3), longer is refused with a 400.
encodingNoEncoding of audioBase64. mp3/opus require ffmpeg (not yet wired in MVP).
languageNoLanguage override for this utterance (default: session language)
sessionIdYesSession ID from open_voice_bridge
audioBase64NoPre-rendered audio bytes, base64 (mode 2). Use with 'encoding'.
voiceDescriptionNoOmniVoice voice-design words, one per group, separated by commas: male|female; child|teenager|young adult|middle-aged|elderly; very low|low|moderate|high|very high pitch; whisper; american|british|australian|canadian|indian|chinese|korean|japanese|portuguese|russian accent. When OmniVoice speaks the line, any other word is dropped: it speaks in its default voice and the reply carries a warning. When OmniVoice was not ready at open_voice_bridge, a fallback voice speaks and ignores this field.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / text / description
      Previous value: -"Text to speak (mode 1). Uses OmniVoice TTS."New value: +"Text to speak (mode 1). One or two sentences work best; at most 700 speech units (each Chinese, Japanese, Korean or Thai character counts 3), longer is refused with a 400."
  2. Changed1 schema field changed
    • changedInput schema / properties / voiceDescription / description
      Previous value: -"Free-form voice description for TTS (e.g., 'calm female voice')"New value: +"OmniVoice voice-design words, one per group, separated by commas: male|female; child|teenager|young adult|middle-aged|elderly; very low|low|moderate|high|very high pitch; whisper; american|british|australian|canadian|indian|chinese|korean|japanese|portuguese|russian accent. When OmniVoice speaks the line, any other word is dropped: it speaks in its default voice and the reply carries a warning. When OmniVoice was not ready at open_voice_bridge, a fallback voice speaks and ignores this field."
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses rich behavioral traits beyond the sparse annotation: the callee cannot interrupt while the agent speaks, their speech is not heard during speech and for under a second after, the call returns only when playback finishes, and partial-failure errors require not repeating the start. It also states the 700-unit/roughly 45-second limit and explains billing coverage. These are exactly the operational details an agent needs for safe use.

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?

The description is front-loaded with purpose and the two modes, then layers operational constraints in a logical order. Although it is long, every sentence contributes useful behavioral or usage information, and there is no redundant restatement of the tool name.

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?

For a complex real-time voice tool with no output schema and only a generic openWorldHint annotation, the description covers modes, length limits, turn-taking behavior, partial failure handling, and billing. It also states that the call returns when speech playback finishes, which substitutes for an output schema at the level needed to call the tool 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 description coverage is 100%, so the schema already documents all six parameters comprehensively. The description reinforces the two main modes and the text-length limit, but it does not add meaning for parameters such as language or voiceDescription. With the schema carrying the parameter burden, baseline 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 states a specific verb and resource: inject audio into an open Voice Bridge call. It clearly distinguishes two operating modes (text synthesis versus base64 audio with encoding) and makes it obvious this is not a standalone TTS tool. An agent can identify the operation without opening the 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?

The description gives clear context for when to use the tool, including that it is for an open Voice Bridge call and that replies should be one or two sentences because the call is turn-based. It also explains how to choose between the text and audio modes and how to handle longer messages. It does not explicitly name sibling alternatives such as text_to_speech for standalone synthesis, so it stops short of full when-not guidance.

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.