Skip to main content
Glama

start_meeting

Start a synchronous conversation with an agent (e.g., CFO or product lead) and get a meeting ID for follow-up messages. Use debate mode to stress-test your agenda instead of executing it.

Instructions

Start a meeting with an agent. Returns a meeting ID for follow-up messages. Use this to begin a synchronous conversation with another agent (CFO, FP&A, Product, etc.). Pass mode: "debate" to have the agent stress-test your agenda as a challenger instead. Pass prototype: true to have the agent show its proposals as ephemeral prototypes that you assess.

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": {
      "agent": "<agent>",
      "agenda": "<agenda>"
    },
    "name": "start_meeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
duelNoOptional duel id (duel-...) from ROUNDTABLE_HOME/duels to make the focus of this session: a scrubbed, size-capped brief of the duel (teams, artifacts, verdicts, tally, dissents) is added to the context every participant sees, as untrusted content to discuss. An unknown or invalid id is an error before any provider call.
modeNodebate: the agent acts as a challenger and stress-tests your agenda instead of helping execute it. Default: standard.
agentYesAgent identifier or path to prompt file. Examples: "cfo", "fpa", "product"
modelNoModel id. Defaults: claude-sonnet-5-5 (anthropic), gpt-5.6-luna (openai), zai-org/GLM-5.3 (together), qwen/qwen3-235b-a22b-instruct-2507 (replicate), qwen3:14b (ollama), default (openai_compatible). Model aliases: "opus" (claude-opus-5-5), "sonnet" (claude-sonnet-5-5), "haiku" (claude-haiku-5-5). Replicate accepts owner/name, owner/name:version, or a https://replicate.com/owner/name URL.
agendaYesThe topic, question, or task to discuss with the agent.
publicNoDefault false. Only set true when the human explicitly asks for a public session. When true, the whole session is posted live to the configured public channel and is world-readable: the topic/agenda, every agent reply, every message you send with say/nudge, and the summary. The context argument is never posted, but agents may paraphrase it in their replies, so keep context generic. Never include personal information, credentials, or private code anywhere in a public session. The result includes public.url so the human can watch live.
contextNoOptional additional context, document content, or data to share.
base_urlNoOnly with provider "openai_compatible": base URL of an OpenAI-compatible /v1 endpoint (e.g. http://localhost:1234/v1). Overrides OPENAI_COMPATIBLE_BASE_URL for this session/call. OPENAI_COMPATIBLE_API_KEY, if set, is sent only to the OPENAI_COMPATIBLE_BASE_URL origin or one listed in ROUNDTABLE_OPENAI_COMPATIBLE_TRUSTED_ORIGINS; any other base URL gets no Authorization header and must be https (http only to loopback, or to private addresses with ROUNDTABLE_ALLOW_PRIVATE_BASE_URLS=1), never a cloud metadata or (without that setting) private address.
providerNoLLM provider. Omit or use auto for provider judgment (the router picks a healthy provider per seat and reports why in a routing block); otherwise the chosen provider is used as given. Options: auto; anthropic; openai; together (Together AI — any Together model id, e.g. zai-org/GLM-5.3 or Qwen/...); replicate (owner/name, owner/name:version, or https://replicate.com/owner/name); ollama (local, only when reachable); openai_compatible (any /v1/chat/completions server — set OPENAI_COMPATIBLE_BASE_URL or pass base_url).
prototypeNoDefault false. Prototype mode: agents show proposals as ephemeral artifacts — a scaled-down page shown in a sandboxed frame on a localhost board, the code/IaC that would produce the proposal (never executed), a Mermaid diagram, or a text draft — and the other participants (in meetings: you) give verdicts; the proposer then revises, scraps or shortlists. Results include a prototypes block with the board URL: show it to the human. Prototypes are destroyed as soon as assessment completes. Do not relay the human's feedback on prototypes into the session until it ends; end_* lists outcomes and the shortlist for the human. Combinable with public (public posts get code, diagram links and screenshots of web prototypes, never the localhost board). Not supported with mode conversation.
connectorsNoOptional names of configured MCP connectors (roundtable config set connector) that every seat may call as tools during its turn. Only read-only tools are offered unless the connector's config lists more; tool results are untrusted data and are scrubbed. Seats on providers without tool support (Replicate) speak without them. An unknown connector is an error before any provider call.
page_checkNoCheck web prototypes in local headless Chrome when available (default true).
duel_sourceNoDefault true; only with duel. The duel brief is resent on every turn to every participant (a full brief can be about 20k tokens per turn). Set false to leave out artifact file contents and keep titles, file names and sizes, verdicts, tally and dissents.
debate_focusNoOptional: what the challenge should concentrate on (only used with mode debate).
seat_connectorsNoOptional per-seat limits, used with connectors: a map from a seat (agent) name to the subset of connectors that seat may call, e.g. {"ada": ["figma"], "bob": ["jira"]}. A seat not listed gets all of the session's connectors; an empty list gives that seat none. Every connector named must also be in connectors, and every seat must be at the table; otherwise the call fails before anything starts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv2.0.0
    • changedInput schema / properties / base_url / description
      Previous value: -"Only with provider \"openai_compatible\": base URL of an OpenAI-compatible /v1 endpoint (e.g. http://localhost:1234/v1). Overrides OPENAI_COMPATIBLE_BASE_URL for this session/call. OPENAI_COMPATIBLE_API_KEY, if set, is sent as the bearer token to whichever base URL is used."New value: +"Only with provider \"openai_compatible\": base URL of an OpenAI-compatible /v1 endpoint (e.g. http://localhost:1234/v1). Overrides OPENAI_COMPATIBLE_BASE_URL for this session/call. OPENAI_COMPATIBLE_API_KEY, if set, is sent only to the OPENAI_COMPATIBLE_BASE_URL origin or one listed in ROUNDTABLE_OPENAI_COMPATIBLE_TRUSTED_ORIGINS; any other base URL gets no Authorization header and must be https (http only to loopback, or to private addresses with ROUNDTABLE_ALLOW_PRIVATE_BASE_URLS=1), never a cloud metadata or (without that setting) private address."
    • addedInput schema / properties / connectors
      Added value: +{
      +  "description": "Optional names of configured MCP connectors (roundtable config set connector) that every seat may call as tools during its turn. Only read-only tools are offered unless the connector's config lists more; tool results are untrusted data and are scrubbed. Seats on providers without tool support (Replicate) speak without them. An unknown connector is an error before any provider call.",
      +  "items": {
      +    "maxLength": 32,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "maxItems": 8,
      +  "type": "array"
      +}
    • addedInput schema / properties / debate_focus
      Added value: +{
      +  "description": "Optional: what the challenge should concentrate on (only used with mode debate).",
      +  "type": "string"
      +}
    • addedInput schema / properties / duel
      Added value: +{
      +  "description": "Optional duel id (duel-...) from ROUNDTABLE_HOME/duels to make the focus of this session: a scrubbed, size-capped brief of the duel (teams, artifacts, verdicts, tally, dissents) is added to the context every participant sees, as untrusted content to discuss. An unknown or invalid id is an error before any provider call.",
      +  "type": "string"
      +}
    • addedInput schema / properties / duel_source
      Added value: +{
      +  "description": "Default true; only with duel. The duel brief is resent on every turn to every participant (a full brief can be about 20k tokens per turn). Set false to leave out artifact file contents and keep titles, file names and sizes, verdicts, tally and dissents.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / mode
      Added value: +{
      +  "description": "debate: the agent acts as a challenger and stress-tests your agenda instead of helping execute it. Default: standard.",
      +  "enum": [
      +    "standard",
      +    "debate"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / model / description
      Previous value: -"Model id. Defaults: claude-opus-5 (anthropic), gpt-5.6-luna (openai), zai-org/GLM-5.3 (together), qwen/qwen3-235b-a22b-instruct-2507 (replicate), qwen3:14b (ollama), default (openai_compatible). Anthropic also accepts the aliases \"opus\" (claude-opus-5) and \"sonnet\" (claude-sonnet-5). Replicate accepts owner/name, owner/name:version, or a https://replicate.com/owner/name URL."New value: +"Model id. Defaults: claude-sonnet-5-5 (anthropic), gpt-5.6-luna (openai), zai-org/GLM-5.3 (together), qwen/qwen3-235b-a22b-instruct-2507 (replicate), qwen3:14b (ollama), default (openai_compatible). Model aliases: \"opus\" (claude-opus-5-5), \"sonnet\" (claude-sonnet-5-5), \"haiku\" (claude-haiku-5-5). Replicate accepts owner/name, owner/name:version, or a https://replicate.com/owner/name URL."
    • addedInput schema / properties / page_check
      Added value: +{
      +  "description": "Check web prototypes in local headless Chrome when available (default true).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / prototype
      Added value: +{
      +  "description": "Default false. Prototype mode: agents show proposals as ephemeral artifacts — a scaled-down page shown in a sandboxed frame on a localhost board, the code/IaC that would produce the proposal (never executed), a Mermaid diagram, or a text draft — and the other participants (in meetings: you) give verdicts; the proposer then revises, scraps or shortlists. Results include a prototypes block with the board URL: show it to the human. Prototypes are destroyed as soon as assessment completes. Do not relay the human's feedback on prototypes into the session until it ends; end_* lists outcomes and the shortlist for the human. Combinable with public (public posts get code, diagram links and screenshots of web prototypes, never the localhost board). Not supported with mode conversation.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / provider / description
      Previous value: -"LLM provider to use. Default: anthropic. Options: anthropic; openai; together (Together AI — any Together model id, e.g. zai-org/GLM-5.3 or Qwen/...); replicate (owner/name, owner/name:version, or https://replicate.com/owner/name); ollama (local, only when reachable); openai_compatible (any /v1/chat/completions server — set OPENAI_COMPATIBLE_BASE_URL or pass base_url)."New value: +"LLM provider. Omit or use auto for provider judgment (the router picks a healthy provider per seat and reports why in a routing block); otherwise the chosen provider is used as given. Options: auto; anthropic; openai; together (Together AI — any Together model id, e.g. zai-org/GLM-5.3 or Qwen/...); replicate (owner/name, owner/name:version, or https://replicate.com/owner/name); ollama (local, only when reachable); openai_compatible (any /v1/chat/completions server — set OPENAI_COMPATIBLE_BASE_URL or pass base_url)."
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "anthropic",
      -  "openai",
      -  "together",
      -  "replicate",
      -  "ollama",
      -  "openai_compatible"
      -]New value: +[
      +  "auto",
      +  "anthropic",
      +  "openai",
      +  "together",
      +  "replicate",
      +  "ollama",
      +  "openai_compatible"
      +]
    • addedInput schema / properties / public
      Added value: +{
      +  "description": "Default false. Only set true when the human explicitly asks for a public session. When true, the whole session is posted live to the configured public channel and is world-readable: the topic/agenda, every agent reply, every message you send with say/nudge, and the summary. The context argument is never posted, but agents may paraphrase it in their replies, so keep context generic. Never include personal information, credentials, or private code anywhere in a public session. The result includes public.url so the human can watch live.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / seat_connectors
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Optional per-seat limits, used with connectors: a map from a seat (agent) name to the subset of connectors that seat may call, e.g. {\"ada\": [\"figma\"], \"bob\": [\"jira\"]}. A seat not listed gets all of the session's connectors; an empty list gives that seat none. Every connector named must also be in connectors, and every seat must be at the table; otherwise the call fails before anything starts.",
      +  "patternProperties": {
      +    "^.+$": {
      +      "items": {
      +        "maxLength": 32,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "maxItems": 8,
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare non-read-only, open-world, non-idempotent and non-destructive, and the description adds genuinely new behavior: a meeting ID is returned for follow-up, debate mode makes the agent a challenger rather than a helper, and prototype artifacts are ephemeral and destroyed after assessment. The significant remaining gap — that a session blocks/streams interactively and that follow-up turns matter — is partly carried by the schema rather than the description.

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?

Four short sentences, front-loaded with the action and the return value, then the two behavioral variants. The mode and prototype sentences largely duplicate the parameter descriptions, so a little of the text is redundant, but nothing is unclear or padded.

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 15-parameter, open-world, side-effecting tool with two required arguments, the description covers what it does, what it returns, and the two non-obvious behavioral switches. Since the schema documents every parameter exhaustively and there is no output schema, an agent has what it needs to call it 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 15 parameters in depth (including the public-posting warning and base_url trust rules). The description's mentions of mode: 'debate' and prototype: true restate schema semantics without adding format, defaults, or interaction detail, 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 specific verb and resource ('Start a meeting with an agent') plus a concrete outcome ('Returns a meeting ID for follow-up messages') and characterizes it as a synchronous conversation with another agent. It never names which sibling it is not — despite start_local_meeting, start_collaboration, start_duel and start_preview sitting alongside it — so the agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Gives a positive usage cue ('begin a synchronous conversation with another agent') and two mode-level alternatives (debate to stress-test, prototype to show proposals), which is more than nothing. But there is no when-not guidance and no routing versus the very similar start_local_meeting or start_collaboration, so selection among siblings is left to inference.

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