Skip to main content
Glama

Add Team Member

team_add_member

Add a member with an admin, member, or viewer role, optionally with a display name and workspace; the first user becomes admin when the team database is empty. Requires TEAM_DB_PATH.

Instructions

Add a new member to the team with a specific role. Bootstraps the first user as admin if table is empty. Requires TEAM_DB_PATH.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "team_add_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoThe role to assign (admin, member, viewer)
authorNoThe author ID/username to add
display_nameNoOptional display name
workspace_idNoOptional workspace isolation identifier (e.g. "alpha"). Do not use numeric project IDs or "workspace" as the key.

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
memberNo
detailsNoAdditional error context
messageNo
successYes
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv9.1.0
    • changedInput schema / properties / role / description
      Previous value: -"The role to assign"New value: +"The role to assign (admin, member, viewer)"
    • removedInput schema / properties / role / enum
      Removed value: -[
      -  "admin",
      -  "member",
      -  "viewer"
      -]
    • removedInput schema / required
      Removed value: -[
      -  "author",
      -  "role"
      -]
  2. First observedv9.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds genuine context on top: the bootstrapping rule where an empty table makes the first user admin regardless of the requested role, plus the TEAM_DB_PATH environment requirement. It stops short of saying how duplicate authors are handled.

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?

Three short sentences: purpose first, the non-obvious bootstrap behavior second, the environment prerequisite last. Nothing is redundant and nothing important is buried.

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?

With an output schema present there is no need to describe return values, and annotations handle the mutation profile, so the remaining burden is small. The definition covers the surprise case (first-user admin promotion) and the env dependency, leaving only duplicate-handling and role-override explicit documentation as gaps.

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%, including role values and the workspace_id caveat, so the schema carries parameter meaning. The description adds only the implicit override of role during bootstrap; it says nothing about author being de facto required despite the schema listing zero required parameters.

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 uses a specific verb and resource ("Add a new member to the team") and narrows scope with "with a specific role." That is enough to distinguish it from team_remove_member, team_update_member_role, team_list_members and team_get_member, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Use is implied by the verb: call this when onboarding a member. There is no explicit when-not guidance, no mention of what happens if the member already exists (relevant given idempotentHint=false), and no pointer to team_update_member_role for changing an existing role.

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