Skip to main content
Glama

Join a distribution squad with an invite code

join_space
Idempotent

Join a ProductClank space (a community's distribution squad) for the connected user with the invite code its leader shared. Use it when the user says they were invited to a squad, a space or a community and gives a code. After the join, the space's work is listed for the user: reply and quote drafts in find_opportunities (campaign.space set) and content or take-action campaigns in find_open_campaigns (is_community: true). The user chooses which ones to help with. Calling it again for a space the user is already in is safe (already_member: true). Free. invalid_code means no space has that code: ask the user to check it with the person who invited them.

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": {
      "invite_code": "<invite_code>"
    },
    "name": "join_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
invite_codeYesThe invite code the space leader shared (letters and digits; case does not matter)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive behavior; the description reinforces idempotence with a concrete signal (already_member: true on re-join), adds a cost statement (free), and documents the invalid_code failure mode plus how to recover. It stops short of describing membership limits, permissions required, or what the join response contains beyond the success flag.

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 purpose, then trigger, then post-join consequences and error handling — nothing is padding. The middle sentence listing the two follow-up tools is dense but each clause maps to a concrete action; only minor tightening is possible.

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

Completeness5/5

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

For a single-parameter mutation with no output schema and full annotation coverage, the description supplies trigger, idempotence, cost, post-join routing and the primary error case. An agent has everything needed to call it and to handle the likely failure.

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?

Only one parameter, and schema coverage is 100%, with the schema already stating that case does not matter. The description adds provenance (the code the space leader shared) and ties the value to the invalid_code outcome, but supplies no format detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource (join a ProductClank space/distribution squad) for a specific actor (the connected user) and identifies the required input (the leader's invite code). The parenthetical gloss of 'space' as 'a community's distribution squad' removes jargon ambiguity, so the tool is distinguishable from setup_content_space and the find_* siblings.

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

Usage Guidelines5/5

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

Gives an explicit trigger: the user says they were invited to a squad, space or community and supplies a code. It also describes what to do afterward and which sibling tools surface the resulting work (find_opportunities with campaign.space, find_open_campaigns with is_community: true), letting the agent route correctly without inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.