Mencoro

Reactivate a member

reactivate_member

Give a suspended member their access to the organization back. memberId is the member id from list_members, not the user id. Requires a confirmationToken: call preview_operation with tool "reactivate_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": "reactivate_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

Behavior4/5

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

Annotations only declare the mutation/idempotency profile; the description adds the mandatory two-step confirmation gate and the authorization requirements, which are the real behavioral constraints. It stops short of saying what exactly is restored (e.g., prior role vs. project access), which is the one remaining unknown for a 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?

Three sentences, front-loaded with purpose, then parameter disambiguation, then the gating workflow and permissions. No filler; each clause adds decision-relevant information.

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 permission-gated mutation with a required confirmation token, the description supplies what the schema and annotations cannot: the preview-then-confirm protocol, the auth requirement, and the id provenance. Return values are covered by the output schema, so nothing essential 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?

Schema coverage is only 25%, so the description must carry the load: it clarifies memberId comes from list_members rather than being a user id, and explains how confirmationToken is obtained. organizationId and requestId are left to the schema, which handles them adequately.

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?

States a specific verb and resource plus the state transition it performs: 'Give a suspended member their access to the organization back.' This is clearly distinguishable from siblings like suspend_member, change_member_role, and invite_member.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit precondition workflow: call preview_operation with tool "reactivate_member" and these arguments, show the returned plan, and only proceed after the user agrees. It also names the required permission (organization:manage) and role (owner), so an agent knows when it cannot call at all.

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.