Skip to main content
Glama

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:

  1. Legacy (strings): participants=["arch-lead", "backend-arch"] Returns dispatch_plan with empty launch_call + deprecation warning.

  2. 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

NameRequiredDescriptionDefault
topicYesMeeting discussion topic
roundsNoCustom round structure e.g. [{"topic": "Stance", "rule": "3 paragraphs per person"}]
team_idNoTeam ID or name (optional, auto-uses active team if empty)
templateNoMeeting template, default "free"free
materialsNoGlobal materials all participants must read (file paths)
team_nameNothe name of the team the meeting belongs to (only for OS-side ownership resolution); not
participantsNoParticipant list — strings (legacy) or structured dicts (recommended)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.2

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does valuable work disclosing that the tool only builds a dispatch_plan rather than launching agents, and that legacy string participants yield an empty launch_call plus a deprecation warning, but it is silent on permissions, whether the meeting is persisted/visible, and failure modes of a clearly mutating operation.

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 purpose and then cleanly enumerated by participant format, with a concrete example that earns its space. Minor waste in the multi-line indented example formatting and the phrase "ready to paste into Agent tool" could be tighter.

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?

Output schema exists, so return values needn't be re-explained, and all seven parameters are documented either in the schema or the description's participant section. The remaining gap is the absence of annotations on a create/mutation tool, with no statement of side effects or required ownership.

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 earns a point by documenting the shape of the structured participant dicts (agent_template, role, context_files, expected_output) which the schema leaves as untyped item objects. It still says nothing about rounds, template, materials, or team_id beyond what the schema already declares.

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 and resource ("Create a team meeting") plus the distinguishing output ("return a ready-to-use dispatch_plan for spawning participant Agents"). An agent can tell this is the meeting-creation entry point and understands it does not itself spawn agents, which separates it from runtime siblings like meeting_send_message or meeting_conclude.

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?

The description implies when to use each participant format and steers away from the legacy format by flagging the deprecation warning, but it never states when to use this tool versus alternatives such as meeting_template_list or the debate tools, nor any preconditions (active team required, etc.).

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

Deploy Server

Other Tools