Skip to main content
Glama
Sign In
Karbon MCP Server

Karbon MCP Server

by Mad-Man-Dan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Remove team member

remove_team_member

Remove a user from a team by their UserKey. Team membership affects work visibility and assignment, so confirm with the user before making changes.

Instructions

Remove a user from a team by their UserKey. Team membership can affect work visibility and assignment — confirm with the user before changing it.

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": {
      "teamKey": "<teamKey>",
      "UserKey": "<UserKey>"
    },
    "name": "remove_team_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
UserKeyYesUserKey of the user to remove
teamKeyYesThe Karbon TeamKey

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description provides some behavioral context by noting that team membership affects 'work visibility and assignment' and advising confirmation. It does not disclose whether the operation is permanent, reversible, or requires specific permissions, but the caution implies significance.

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?

The description is concise with two sentences: the first states the core action, the second provides important advisory context. No unnecessary words, front-loaded with the primary purpose.

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?

Given no annotations or output schema, the description covers the basic action and one behavioral caution. It lacks details on return values, reversibility, or prerequisites, but is adequate for a straightforward parameter schema.

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 the schema already documents both parameters. The description adds no additional semantic detail beyond mentioning UserKey. Baseline score of 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 clearly states 'Remove a user from a team by their UserKey', specifying the action and identifier. It distinguishes the tool from its sibling 'add_team_members' by implication, but does not explicitly differentiate or mention alternatives.

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?

The description advises confirming with the user before changing membership, indicating appropriate usage context. However, it does not specify when to use this tool versus alternatives like add_team_members or provide exclusion scenarios.

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