Skip to main content
Glama

Add team member

team_addMember

Put a member of the organization on a team, which gives them every wiki the team is granted. Requires a maintainer of the team or an organization owner. Recorded in the organization's audit log.

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": {
      "slug": "<slug>",
      "userId": "<userId>",
      "org": "<org>"
    },
    "name": "team_addMember"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose people, teams and access to use. Required on every call, even when only one organization is listed; a path never names it.
slugYesThe team's slug, as team_list gives it (platform).
userIdYesThe person's user id, as members_list gives it (user_2abc). Never a name or an email.
maintainerNotrue to add them as a maintainer, who may change the team and its members; a plain member when left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), it discloses meaningful behavior: the access implication of team membership, the authorization requirement, and that the action is written to the organization's audit log. It does not cover idempotency — whether re-adding an existing member errors or is a no-op — which matters for a mutation tool.

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?

Three short sentences, front-loaded with the action and its effect, then preconditions, then side effect — no filler. Slightly denser than needed could be, but nothing is wasted.

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

Completeness3/5

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

For a non-destructive mutation with a fully documented schema and no output schema, the description covers auth and audit-trail consequences well. It leaves gaps on duplicate-membership behavior and error/failure modes, which an agent calling this against a production org would benefit from knowing.

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 all four parameters, including the maintainer flag and the userId format, are already documented in structured data. The description adds only indirect meaning by explaining what the team membership confers, and does not clarify parameter interactions or defaults. 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?

A concrete verb plus resource ('Put a member of the organization on a team') followed by the actual effect ('gives them every wiki the team is granted'), which lets an agent understand the outcome, not just the operation. It does not explicitly distinguish itself from siblings like team_setMaintainer or team_removeMember, even though the optional maintainer flag overlaps with the former.

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?

States a clear precondition — 'Requires a maintainer of the team or an organization owner' — which tells the agent when the call is permitted. It stops short of routing guidance such as when to prefer team_setMaintainer for granting maintainer rights, or what to do when the person is already on the team.

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