Skip to main content
Glama

Join Group

join_group
Destructive

Join a self-signup student group by previewing the request and confirming, so groupmates and instructors see your membership.

Instructions

Join a self-signup student group. Groupmates and instructors see that you joined. [NEEDS CONFIRMATION: call it once for a preview and a confirm_token, show the preview to the user, and only if they say yes call it again with the same arguments, confirm=true and that confirm_token. Apps that can ask the user directly show a confirmation instead.]

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": {
      "group_id": "<group_id>"
    },
    "name": "join_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
group_idYesID of the open group to join (numeric string).
confirm_tokenNoThe one-time token from the preview. Only use it after the user has said yes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to actually execute. Omit or set false to get a dry-run preview first."New value: +"Set to true together with confirm_token to carry out a request you already previewed."
    • addedInput schema / properties / confirm_token
      Added value: +{
      +  "description": "The one-time token from the preview. Only use it after the user has said yes.",
      +  "type": "string"
      +}
  2. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / group_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"ID of the open group to join (numeric string)."
  3. First observedv1.0.1

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare a non-idempotent, destructive, open-world mutation, and the description adds meaningfully beyond them: the social consequence ('groupmates and instructors see that you joined') and the mandatory two-phase preview/confirm flow with a one-time token. That is exactly the kind of irreversible-effect and precondition context an agent needs before mutating state.

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?

Two sentences, front-loaded with the action and consequence, then the workflow. The bracketed '[NEEDS CONFIRMATION: ...]' block is slightly awkward metadata-style framing, but every clause in it carries operational instructions rather than filler.

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?

No output schema exists, and the description covers the mutation's side effects and the confirm handshake, which is the critical missing piece for a destructive tool. It does not say what the preview response contains besides the token, leaving the agent to discover the preview shape empirically, but that is a minor gap for a 3-parameter tool.

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 100%, so group_id, confirm, and confirm_token are already documented in structured fields. The description reinforces the confirm/confirm_token contract in prose but adds no format, range, or edge-case meaning (e.g. token expiry, token reuse) beyond the schema.

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?

States a specific verb ('Join') and resource ('self-signup student group'), and the 'self-signup' qualifier usefully scopes it away from admin-driven or invitation-only group additions. It does not name its closest sibling (leave_group) or otherwise differentiate explicitly, so it stops 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 Guidelines4/5

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

Gives an unusually explicit call pattern: first call is a preview returning a confirm_token, and a second call with confirm=true and the same arguments only after the user says yes, with a noted variant for apps that can prompt users directly. It does not cover when NOT to use it (already a member, group closed or full, non-self-signup groups), which keeps it from a 5.

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