Skip to main content
Glama

Coline

Add someone to a team

add_team_member

Adds a workspace member to a team, as a member by default.

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": {
      "workspace": "<workspace>",
      "teamId": "<teamId>",
      "userId": "<userId>"
    },
    "name": "add_team_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNo
teamIdYesTeam id from list_teams.
userIdYesThe person's user id (userId from list_members).
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
memberYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare it as a non-read-only, non-destructive, non-idempotent mutation, and the description usefully adds that role defaults to 'member'. It says nothing about what happens when the user is already on the team (relevant given idempotentHint=false), whether the person is notified, or what permissions are required.

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?

A single front-loaded sentence with zero filler; the default-role clause is the one detail worth carrying in prose.

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?

An output schema exists, so return values need no explanation, and the parameter sourcing is handled by the schema. For a team-membership mutation with idempotentHint=false, however, the description leaves the duplicate-membership outcome and permission prerequisites unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75% and documents teamId, userId and workspace sources, but the schema exposes the role enum without stating a default; the description supplies exactly that ('as a member by default'). This is genuine meaning added beyond the input 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 and resource ('Adds a workspace member to a team') plus the default role applied, so the agent knows exactly what the tool accomplishes. It does not name or differentiate against near-neighbors such as invite_member or update_team_member_role, 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no alternative is named, even though siblings like update_team_member_role and invite_member overlap in intent. The only hint of intended usage is the implicit 'this is how you add a new member' framing.

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