meeting_create
Creates a team meeting and returns a ready-to-use dispatch plan for spawning participant agents; supports structured participant roles, context files, and expected outputs.
Instructions
Create a team meeting and return a ready-to-use dispatch_plan for spawning participant Agents.
Supports two participant formats:
Legacy (strings): participants=["arch-lead", "backend-arch"] Returns dispatch_plan with empty launch_call + deprecation warning.
Structured (dicts): participants=[{"name": "arch-lead", "agent_template": "software-architect", "role": "Responsible for evaluating architecture proposals", "context_files": ["docs/arch.md"], "expected_output": "three-paragraph form"}] Returns dispatch_plan with fully populated launch_call.params ready to paste into Agent tool.
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": {
"topic": "<topic>"
},
"name": "meeting_create"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | Meeting discussion topic | |
| rounds | No | Custom round structure e.g. [{"topic": "Stance", "rule": "3 paragraphs per person"}] | |
| team_id | No | Team ID or name (optional, auto-uses active team if empty) | |
| template | No | Meeting template, default "free" | free |
| materials | No | Global materials all participants must read (file paths) | |
| team_name | No | the name of the team the meeting belongs to (only for OS-side ownership resolution); not | |
| participants | No | Participant list — strings (legacy) or structured dicts (recommended) |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||