Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

calls_set_translation_language

Read-onlyIdempotent

Change the target language of an active voice/Meet call's live translator on the fly — no hangup or re-dispatch (also arms translator mode if it isn't already on). Pass the call_id and an ISO language code, e.g. 'th' (Thai), 'ru' (Russian), 'es' (Spanish), 'en' (English). Takes effect within ~10ms — speak and the translation switches to the new language.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
call_idYesThe active call / Meet session call_id (UUID) — e.g. from calls.send_to_meet's session_id or calls.list_active.
languageYesTarget language ISO code: 'th' (Thai), 'ru' (Russian), 'es' (Spanish), 'en' (English), etc.
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. Added

TDQS

B3.3/5.0
Behavior1/5

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

Annotations declare readOnlyHint=true, yet the description describes an operation that mutates live call state: it changes the target language and 'arms translator mode if it isn't already on'. This directly contradicts the read-only claim, which would lead an agent to treat the call as untouched when the tool actually alters what participants hear.

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-loaded with the core action and immediately followed by the key constraint (no hangup/re-dispatch) and the latency expectation. Slightly padded by duplicating the language examples already present in the schema, but no sentence is wasted.

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?

For a 3-parameter tool with full schema coverage and no output schema, the description covers the important runtime behavior: it works on an in-flight call, arms translator mode, and takes effect in ~10ms. It omits error behavior for an invalid language code and the exact response, but those are minor.

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 call_id and language are already documented, and the description merely repeats the same ISO-code examples ('th', 'ru', 'es'). It adds no syntax, validation, or failure semantics beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb+resource+scope: changing the target language of an active voice/Meet call's live translator. It implicitly separates itself from the dispatch path ('no hangup or re-dispatch'), but never addresses the near-identically named sibling calls_set_translation_languages (plural), which is the most likely confusion point for an agent choosing a tool.

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 context for use (an active call whose translator is running) and states that it also arms translator mode if it is off, so the agent knows it works pre-emptively. It implicitly rules out the alternatives ('no hangup or re-dispatch') but never names a sibling tool or an explicit when-not condition.

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