Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

calls_dispatch_agent

Read-onlyIdempotent

Send a workspace AI agent into a live call — ONE tool for every surface; target decides where: a Google Meet or Microsoft Teams link → meeting bot; a Telegram @group / t.me link / chat_id / t.me/call slug → Telegram group voice chat or conference; 'new' → creates a NEW Telegram conference call and returns its shareable link; a WhatsApp group JID (digits@g.us) → WhatsApp group call; a live session UUID (from calls.list_active), or thread_id of a running call → WAKES the agent on the bot already in that call instead of spawning a second one. For a meeting link the router also checks for a bot already in that meeting and wakes it rather than double-joining. Always pass agent_id (from agents.list). For a live TRANSLATOR use calls.dispatch_translator instead. agent_id must be an ACTIVE agent of this workspace — a system template is refused (create an agent from it first with agents.create). To take the agent off the call again while the bot keeps transcribing, use calls.dismiss_agent.

Input Schema

NameRequiredDescriptionDefault
titleNotarget='new' only: label for the new conference.
targetNoWhere to send the agent: a Google Meet or Microsoft Teams link, a Telegram @group / t.me link / chat_id / t.me/call slug, 'new' for a fresh Telegram conference, a WhatsApp group JID (digits@g.us), or a live session UUID to wake the agent on a running call. Omit only when passing thread_id.
agent_idYesID of an active agent in this workspace (from agents.list). Any active agent can be dispatched — a voice trigger is NOT required.
greetingNoFirst line the agent speaks on a 1:1 call. Omit to use the agent's configured default greeting.
thread_idNoInbox thread id of a RUNNING call — wakes the agent on the bot already in it. Alternative to a session UUID target.
vision_modeNoScreen-share capture mode (Meet + Telegram spawns): 'off', 'on_demand' (agent can call vision_query), 'continuous_0_3fps' (ambient scene captures each turn). OMIT to use 'off' (the default).
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
instructionsNoTask brief for the agent, e.g. 'take notes and answer questions about the roadmap'. On a spawn it is woven into the voice system prompt; on a wake it is the kickoff turn the agent responds to. OMIT for a generic listening/greeting agent.
start_immediatelyNoSpawn routes only: if true the agent starts talking as soon as it joins instead of waiting to be addressed. OMIT (default false) to stay silent until addressed. Wake routes always speak immediately.
channel_account_idNoTelegram routes: workspace Telegram account that joins/founds the call. Optional with exactly one Telegram account; required with several.

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

TDQS

A4/5.0
Behavior1/5

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

Annotations declare readOnlyHint=true and idempotentHint=true, but the description describes a side-effecting operation: it spawns meeting bots, creates a NEW Telegram conference call and returns a shareable link, and joins WhatsApp groups. Resource creation and joining live calls are neither read-only nor idempotent, so the description directly contradicts the declared safety profile.

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 core verb and the routing key ('target decides where') before the branch list, and every branch carries actionable info. It runs long and re-enumerates target values already documented in the schema, which is the only real waste.

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?

Covers the full decision surface for a 10-parameter router with no output schema: prerequisites, spawn vs wake behavior, sibling alternatives for translator and dismissal, and the default greeting/instructions fallbacks. Hard to imagine an agent calling this incorrectly from the description alone, aside from the annotation mismatch.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: the cross-parameter rule that agent_id must be an active agent of this workspace (system templates are refused), the wake-vs-spawn distinction between session UUID and thread_id, and the instruction to always pass agent_id. It is largely duplicative on the target enumeration but adds real routing semantics.

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?

Opens with a concrete verb+resource ('Send a workspace AI agent into a live call') and explicitly frames itself as the single router for every surface. Each target variant (Meet/Teams link, Telegram group, 'new' conference, WhatsApp JID, live session UUID/thread_id) is enumerated, so an agent can match its situation 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 Guidelines5/5

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

Gives explicit when-to-use-which routing, tells the caller to use calls.dispatch_translator for translator work and calls.dismiss_agent to remove the agent, and states prerequisites for agent_id (must be an ACTIVE agent; templates refused, create from template first). It also explains the wake-vs-spawn preference so a second bot isn't double-joined.

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