Skip to main content
Glama

Manage team invite link and join requests

manage_join_access
Destructive

For an organization: get, renew, or turn off the reusable team invite link (anyone with the link can join while seats are free), and list, approve, or decline requests to join from people at a company email domain. Only an owner or an admin can change the link or decide requests.

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": {
      "org_id": "<org_id>",
      "action": "<action>"
    },
    "name": "manage_join_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoFor list_requests: include decided requests too.
roleNoFor new_link: the role new people get. Default member.
actionYesWhat to do. new_link makes a new link and stops the old one.
org_idYesOrganization id from list_organizations.
request_idNoFor approve or decline: the id from list_requests.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds genuinely useful context beyond them: new_link invalidates the previous link, joining consumes seats, and an owner/admin role is required. It does not say whether approve/decline can be undone or what happens to pending requests when the link is turned off, which keeps it from a 5.

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 tight sentences front-load the two resource groups and then the permission constraint, with no filler. The nested parentheticals are slightly dense but each carries real information.

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?

Six actions are packed into one mutating tool with no output schema, so the description must carry the full burden. It enumerates every action, states the side effect of link rotation, the seat constraint, and the authorization requirement, which is enough for an agent to call it correctly.

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 every parameter including the action enum and the default role is already documented. The description adds only marginal semantics (seat availability, decision authority) and no extra detail on all, role, or request_id. Baseline 3 is appropriate.

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 description names specific verbs (get, renew, turn off, list, approve, decline) against two concrete resources: the reusable team invite link and join requests. The parenthetical 'anyone with the link can join while seats are free' distinguishes link-based joining from per-person invites. It stops short of naming a sibling such as invite_member to make the boundary explicit, so a 4 rather than 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?

It gives clear operating context: the link is reusable and seat-limited, requests come from company email domains, and only owners/admins may change the link or decide requests. What is missing is an explicit statement of when to use this versus invite_member for a single person, but the permission prerequisite and per-action framing make usage inferable.

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.

Resources