Skip to main content
Glama

Remove a person from the Project

remove_user
Destructive

Remove a member from this Project and release their seat through Ekaya Central, or cancel an invitation, which also removes them from the Project and releases their seat if they had already accepted it. It also tries to revoke the credentials they connected to this Project's datasources; the removal succeeds even if that revocation fails, and re-inviting the person and removing them again retries it. If Central refuses, the person stays in this Project. For removal_incomplete, Central may have released the seat; remove them again to finish. For central_membership_may_remain, the person was removed from this Project; Central no longer lists the invitation, so the account that accepted it could not be identified and a membership there may remain: check this Project's Users in Ekaya Central.

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": {
      "user_id": "<user_id>"
    },
    "name": "remove_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesThe id list_users reports for the member or invitation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: seat release via Ekaya Central, best-effort credential revocation that does not block removal, retry-on-reinvite semantics, and atomic failure when Central refuses. It also enumerates the partial-outcome states (removal_incomplete, central_membership_may_remain) and what each implies about seat/account state — exactly the context the destructive/openWorld annotations cannot convey.

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?

Front-loads the core action, then the caveats, and nearly every clause carries distinct behavioral information. The first sentence is an overlong run-on and the outcome codes are introduced without stating where they appear, but the density is justified for a destructive operation with partial-failure modes.

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?

There is no output schema, yet the definition still explains what the caller can observe afterwards and how to interpret and remediate each partial outcome. Combined with the annotation safety profile, an agent has everything needed to decide whether to call it and how to react to results.

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 coverage is 100% and the single parameter already documents that it is the id reported by list_users for a member or invitation. The description adds only the pointer to 'this Project's Users in Ekaya Central' for the orphaned-membership case, which is marginal beyond the 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?

Names a specific verb and resource ('Remove a member from this Project') and covers both modes: removing an existing member and cancelling a pending invitation. It does not explicitly distinguish itself from the similarly-named sibling remove_role_members, so an agent must infer that this tool operates on the Project membership rather than on a role.

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?

Gives clear conditional guidance: if Central refuses, nothing changes; if removal_incomplete, remove again to finish; if central_membership_may_remain, check Users in Ekaya Central. It does not state when a different tool (e.g., a role-membership removal) should be used instead, leaving that routing to inference.

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