Skip to main content
Glama

Take someone out of a Space

spaces_remove_member
Destructive

Remove a member from a Space. Owner only. The person's documents in the Space pass to the Space owner, so nothing leaves the Space.

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": {
      "spaceId": "<spaceId>",
      "userId": "<userId>"
    },
    "name": "spaces_remove_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesA member userId from spaces_get_space.
spaceIdYesThe Space id, from spaces_list_spaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is carried by structured data. The description does add genuinely useful behavior beyond that: the ownership requirement and the fact that the removed person's documents transfer to the Space owner rather than leaving the Space. It nonetheless omits whether the removal is reversible, whether the member is notified, or whether their access is revoked immediately.

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 with no filler, and the action plus the ownership constraint are front-loaded. The side-effect sentence is placed last where it belongs. Nothing is wasted, though the phrasing is dense enough that the transfer rule takes a moment to parse.

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 two-parameter destructive mutation with full schema coverage and no output schema, the description covers the two things that matter most: who may call it and where the member's documents go. It stops short on post-conditions an agent would want before a destructive call — reversibility of the removal and what the member retains — so it is close to but not fully complete.

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%, and both parameters already document their provenance ("from spaces_get_space", "from spaces_list_spaces"), which is better than most. The description adds no parameter-level meaning at all, so the baseline of 3 applies — the schema, not the prose, is doing the work.

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 states a specific verb and resource ("Remove a member from a Space"), which is unambiguous and clearly distinct from spaces_invite_members or spaces_remove_note. It does not explicitly distinguish itself from spaces_leave_space (the self-service counterpart), which is the sibling most likely to be confused with it, so it falls 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 Guidelines3/5

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

"Owner only" gives a real precondition — the calling agent knows it must be the Space owner to invoke this. However, there is no statement of when to use this versus spaces_leave_space, nor any note on preconditions such as the member existing or whether re-invitation is possible, so condition-to-tool routing is only implied.

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