docmost-community-mcp

by dilruwanm

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

remove_space_member

Destructive

Remove a user or group from a space to revoke their access. Provide the space ID and either user ID or group ID.

Instructions

Remove a user or group from a 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": {
      "space_id": "<space_id>"
    },
    "name": "remove_space_member"
  }
}

Input Schema

Name	Required	Description
`user_id`	No
`group_id`	No
`space_id`	Yes	Space UUID or slug

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 26, 2026

TDQS

C2.8/5.0

Behavior2/5

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

The description adds no behavioral context beyond what annotations already declare. It doesn't explain consequences of removal, permission requirements, reversibility, or effects on the member's access, which is relevant given destructiveHint=true.

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?

One short sentence with the operation and target front-loaded, and no filler. Both halves of the description earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive tool with no output schema and sparse parameter metadata, the description is too thin. It omits the relationship between user_id and group_id, the success/return behavior, and the practical implications of removing a member.

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

Parameters2/5

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

Schema description coverage is only 33%, and the description does not compensate. It says 'user or group' but does not clarify whether user_id and group_id are mutually exclusive, whether at least one is required, or what happens if both or neither are supplied.

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 ('Remove') and resource ('a user or group from a space'), making the core operation unambiguous. It is clearly distinct from siblings like add_space_members or update_space_member_role, though it does not explicitly name an alternative.

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 guidance on when to use this tool versus sibling membership tools, and no exclusions or prerequisites are given. The intended usage must be inferred entirely from the verb and tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.