Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

calls_mute_translation_tts

Read-onlyIdempotent

Mute or unmute an active call's live-translation TTS. scope='call' (default, Google Meet sessions ONLY): the translator goes silent INSIDE the call — participants hear no bot voice, in-flight audio is cut immediately, but translation audio + subtitles remain available in the app (listen overlay). scope='everywhere' (any channel): stop synthesizing entirely from the next utterance — subtitles only, no audio anywhere. muted=false reverses either. Translation itself keeps running throughout.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mutedYestrue to mute, false to unmute.
scopeNo'call' (default; Google Meet only): silent in the call only — app audio + subtitles keep flowing. 'everywhere' (any channel): no TTS synthesis at all (subtitles only). OMIT to use the 'call' default.
call_idYesThe active call / Meet session call_id (UUID) — e.g. from calls.send_to_meet's session_id or calls.list_active.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. Changed1 schema field changed
    • changedInput schema / properties / scope / description
      Previous value: -"'call' (default; Google Meet only): silent in the call only — app audio + subtitles keep flowing. 'everywhere' (any channel): no TTS synthesis at all (subtitles only)."New value: +"'call' (default; Google Meet only): silent in the call only — app audio + subtitles keep flowing. 'everywhere' (any channel): no TTS synthesis at all (subtitles only). OMIT to use the 'call' default."
  5. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover idempotency and non-destructiveness, yet the description adds real behavioral detail: in-flight audio is cut immediately, subtitles and app-side listen overlay survive the 'call' mute, and translation itself keeps running. The only friction is the mild tension with readOnlyHint=true for an operation that toggles live audio behavior, though no persistent data is mutated.

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?

Front-loads the purpose in the first clause, then elaborates scope behavior and reversibility. Dense but each sentence carries an actionable distinction between the two scopes, with little filler.

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?

No output schema exists, but the description covers both modes, the default, reversibility, and the ongoing-translation behavior, which is what an agent needs to call it correctly. Minor omissions (prerequisites like an active translation session, invalid call_id behavior) keep it just under complete.

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 call_id, muted, scope, and in_workspace. The description largely restates the scope semantics rather than adding syntax or edge-case meaning, 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 pair (mute/unmute) and a precise resource (an active call's live-translation TTS), immediately distinguishing it from sibling tools like calls_set_translation_language or calls_hangup. The scope semantics make the boundary of the operation explicit.

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?

Gives clear when-to-use conditions for each mode: scope='call' is Google Meet sessions ONLY, scope='everywhere' works on any channel. It also states muted=false reverses either, so the agent knows both directions. It does not name a sibling alternative or an explicit when-not-to-use case, so it falls short of a 5.

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

All dialogbrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources