Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

calls_set_translation_languages

Read-onlyIdempotent

Set the EXTRA target languages an active voice/Meet call's translator produces for the APP ONLY (subtitles + listenable audio in the inbox — NOT spoken into the call). Operators switch between them in the UI. Pass call_id and app_languages (ISO codes, e.g. ['de','fr']); pass [] to drop all extras. Max 4. The primary spoken language is managed by calls.set_translation_language. Takes effect within ~10ms; new languages translate NEW speech only.

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.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
app_languagesYesExtra app-only target languages (ISO codes), e.g. ['de','fr','es']. Pass [] to remove all extras. Max 4.

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

A3.5/5.0
Behavior1/5

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

The description is a mutating setter ('Set the EXTRA target languages', 'Takes effect within ~10ms'), yet the annotations declare readOnlyHint=true. A write operation cannot be read-only, so the description directly contradicts the structured safety signal and could mislead an agent about 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the key distinction (EXTRA app-only vs primary spoken) and the mutating semantics, then constraints and timing. Dense but every clause carries information; only the trailing timing sentence is somewhat tangential.

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 call-scoped config setter with no output schema, it covers effect timing, propagation scope, the 4-language cap, clearing semantics, and the sibling responsible for the primary language. The main gap is behavioral (permissions/state impact), which is muddied by the contradictory readOnly annotation.

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% and the schema already documents call_id, in_workspace, and app_languages (ISO codes, [] to clear, max 4). The description largely restates that (ISO codes, [] to drop, max 4) and adds only the behavioral note that new languages translate new speech, so it does not meaningfully exceed the schema on parameter meaning.

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?

Specific verb (Set) plus resource (extra app-only translation languages) with the scope nailed down: subtitles + listenable audio in the inbox, NOT spoken into the call. It explicitly separates this from calls.set_translation_language, so an agent can distinguish it from its closest sibling without opening a 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?

Clearly states the context of use (extra app-only target languages for an active voice/Meet call) and names the alternative for the primary spoken language via calls.set_translation_language. It also tells the agent how to clear extras ([]). It stops short of an explicit 'use X when / don't use Y when' framing, but routing is unambiguous.

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