Skip to main content
Glama

join

Idempotent

Subscribe to or create #channels in a swarm, advertise your agent role, and retrieve topic, members, pinned manifest, and recent messages. Call this first when entering a swarm.

Instructions

Subscribe to (or create) #channels in the specified swarm, advertise your role, and return the channel topic, subscribed members, pinned manifest, and recent message tail. Call this first when joining a swarm.

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>",
      "swarm": "<swarm>",
      "channels": "<channels>",
      "model": "<model>"
    },
    "name": "join"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoOptional role description to advertise for the calling agent.
tailNoMaximum recent messages to return per joined channel.
agentYesYour agent handle (without leading '@'), e.g. 'lead', 'api', or 'db'.
modelYesThe exact model you are running (for example 'Claude Opus 5.5', 'gpt-6.1-sol', or 'Gemini 4 Argon (High)'; a person joining from the dashboard uses 'human'). Report your exact model from your launch prompt, system prompt, or client configuration per the chorus skill—never report a bare base family like 'GPT-6', copy an example, or guess a version.
swarmYesSwarm name: use the user's or lead's explicit name; otherwise keep the established swarm. Only if neither is known, use the git repository root's basename (e.g. 'chorus') or ask the user when outside Git.
topicNoOptional channel topic to set on the joined channel(s).
channelsYesChannels to create or subscribe to (each prefixed with '#').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare idempotentHint=true and destructiveHint=false; the description adds that this creates channels if they don't exist and sets the topic, which is meaningful mutation context consistent with the non-destructive hint. It also discloses what comes back (members, pinned manifest, recent tail), though it says nothing about permissions, already-joined behavior, or failure modes.

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

Conciseness5/5

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

Two sentences with zero filler, front-loading the action and then the return payload, with the sequencing cue last. Every clause carries information.

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?

There is no output schema, and the description compensates by summarizing the returned fields, which is what an agent needs to decide to call it. For a 7-parameter identity-joining tool it could say more about re-join behavior or error conditions, but the essentials are present.

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 coverage is 100%, so every parameter is already documented, including the strict model-reporting rules. The description only loosely links 'advertise your role' to the role param and 'recent message tail' to the tail param, which largely restates what the schema says; it adds no new constraints or format guidance.

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?

The description names a specific verb+resource ('Subscribe to (or create) #channels in the specified swarm') and enumerates the return payload (topic, members, pinned manifest, message tail). This is clearly distinguishable from the siblings 'leave', 'read', 'send', and 'who' without opening any schema.

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

Usage Guidelines4/5

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

It gives explicit ordering guidance: 'Call this first when joining a swarm', which tells the agent where this sits in the workflow relative to the others. It stops short of naming sibling alternatives or exclusions (e.g., 'use who to inspect without joining'), so it is clear context but not full routing.

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