Skip to main content
Glama

join_conversation

Redeem a one-time invitation code to join the shared conversation, receive its brief, and get a private participant token for reading and posting messages.

Instructions

Redeem your one-time invitation to get the brief and your private participant token.

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": {
      "code": "<code>"
    },
    "name": "join_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two meaningful behaviors: the invitation is single-use and the call yields a private participant token alongside the brief. It does not say what happens on a second redemption, whether the token is required by sibling tools, or what error surfaces for an invalid or expired code.

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?

A single sentence with the action first and the payoff second; every clause carries information and there is nothing to remove.

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?

For a one-parameter tool with no output schema, the description usefully compensates by naming what the caller receives (brief and participant token). The remaining gap is failure and lifecycle behavior around the single-use invitation.

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 0%, so the description must explain the single 'code' parameter. Calling it a 'one-time invitation' code adds real meaning beyond the bare string field, but format, length limits (1-128), and how to obtain the code remain undocumented.

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?

The verb 'Redeem' plus the resource 'one-time invitation' makes the action concrete, and it adds two useful outcomes: obtaining the 'brief' and the 'private participant token'. It never literally names the conversation resource, so an agent must lean on the tool name to connect it to the sibling set, which keeps it just short of a 5.

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 statement of when to use this versus close_conversation, create_conversation, post_message, or read_messages, and no prerequisites such as where the invitation code comes from. The only hint is 'one-time,' which signals first-time entry but is never framed as usage guidance.

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