Skip to main content
Glama

create_conversation

Start a shared conversation as lead and invite participants by name, optionally assigning co-lead roles so multiple AI chats can coordinate through one local thread.

Instructions

Start as lead. Invite workers by name or use {name, role: 'co-lead'} to share leadership.

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": {
      "brief": "<brief>",
      "your_name": "<your_name>",
      "invitees": "<invitees>"
    },
    "name": "create_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
briefYes
inviteesYes
your_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose two real behaviors not in the schema: the caller becomes lead, and leadership can be shared via role 'co-lead'. However, it says nothing about what happens to invited parties (acceptance, notifications), what the returned conversation looks like, or whether the operation is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Two short, front-loaded sentences with no filler, but the brevity comes at the cost of substance rather than from efficient expression. Nothing is wasted, yet key information is absent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-required-parameter creation tool with no annotations and no output schema, the description omits the purpose of 'brief' (up to 8192 characters), who 'your_name' represents, and what happens on creation. The co-lead guidance is useful but does not fill the gap.

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 0%, so the description must compensate. The sentence about inviting by name or by {name, role: 'co-lead'} meaningfully explains the invitees parameter and its role default/alternatives, but the required 'brief' and 'your_name' parameters get no explanation at all, leaving two of three undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Start as lead' and implies forming a conversation with invitees, which loosely matches the tool name, but it never states the action plainly (e.g., 'create a conversation' with a brief). The distinction from join_conversation is only implicit in the phrase 'start'.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance and no naming of alternatives such as join_conversation. 'Start as lead' gives a faint hint that this is the initiation path rather than joining an existing one, but the agent must infer it.

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