Mencoro

Suspend a member

suspend_member

Destructive

Suspend an organization member: they lose access immediately but stay a member, and reactivate_member gives it back. memberId is the member id from list_members, not the user id. Requires a confirmationToken: call preview_operation with tool "suspend_member" and these arguments first, show the returned plan to the user, and call this tool only after the user explicitly agrees. Needs the organization:manage permission and the owner role.

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": {
      "organizationId": "<organizationId>",
      "memberId": "<memberId>",
      "confirmationToken": "<confirmationToken>"
    },
    "name": "suspend_member"
  }
}

Input Schema

Name	Required	Description
`memberId`	Yes
`requestId`	No	Optional idempotency key, 8-255 printable characters. Reuse it only to retry this same call.
`organizationId`	Yes
`confirmationToken`	Yes

Output Schema

Name	Required	Description
`id`	Yes
`role`	Yes
`state`	Yes
`userId`	Yes	The user this membership belongs to
`isActive`	Yes
`joinedAt`	Yes
`projectIds`	Yes	The projects a selected access reaches; empty when the mode is all
`projectAccessMode`	Yes	Which projects of the organization the member reaches: every project, or only projectIds

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 29, 2026

addedOutput schema / properties / projectAccessMode

Added value: +{
+  "description": "Which projects of the organization the member reaches: every project, or only projectIds",
+  "enum": [
+    "all",
+    "selected"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / projectIds

Added value: +{
+  "description": "The projects a selected access reaches; empty when the mode is all",
+  "items": {
+    "format": "uuid",
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "id",
-  "userId",
-  "role",
-  "state",
-  "isActive",
-  "joinedAt"
-]New value: +[
+  "id",
+  "userId",
+  "role",
+  "state",
+  "isActive",
+  "joinedAt",
+  "projectAccessMode",
+  "projectIds"
+]

AddedOct 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond annotations, the description discloses the immediate access-loss effect, that the person remains a member, the confirmation-token workflow, and the organization:manage plus owner-role requirements. These are exactly the behavioral details an agent needs for a destructive membership mutation.

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 dense but front-loaded: effect first, sibling relationship, parameter gotcha, confirmation workflow, and permissions. Every sentence adds operational value, with no filler.

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?

For a destructive, permissioned mutation with an output schema already present, the description covers the key behavioral, authorization, confirmation, and parameter-semantic details. No critical pre-call information is missing.

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?

With only 25% schema description coverage, the description compensates by clarifying that memberId comes from list_members rather than being a user id and by explaining the required confirmationToken workflow. It leaves organizationId implicit and does not define it explicitly, though the surrounding context makes it largely self-evident.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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, explains the immediate effect of suspension, and explicitly distinguishes it from the inverse tool reactivate_member. An agent can identify this as the member-suspension operation without needing to infer from the title.

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?

It gives clear usage context: suspend only after preview_operation and explicit user agreement, and it names reactivate_member as the restoring action. It does not state explicit when-not-to-use conditions, so it falls short of full 5-level routing guidance.

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

All Mencoro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.