Skip to main content
Glama

Enable user

enable_user
DestructiveIdempotent

Re-enable a previously disabled organization member so they can log in and use the platform again. Requires the org_user_id. The organization is fixed by your context — never pass an organization id. You cannot target a user more privileged than yourself, and not your own account. It is refused when the organization's plan has no free seat: its active members already fill the plan's limit (error_code SUBSCRIPTION.SEAT_LIMIT_REACHED, with the limit in error_details); tell the user that no seat is free. Returns a preview unless confirm=true is set.

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": {
      "org_user_id": "<org_user_id>"
    },
    "name": "enable_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet true to perform the action. Omit or false returns a preview only — nothing is written.
org_user_idYesId of the OrganizationUser to enable.
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirm
      Added value: +{
      +  "description": "Set true to perform the action. Omit or false returns a preview only — nothing is written.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as destructive, non-read-only and idempotent, but the description adds behavior the annotations cannot express: the preview-by-default semantics gated on confirm=true, the privilege ceiling, the self-target block, and the seat-limit failure surfaced via SUBSCRIPTION.SEAT_LIMIT_REACHED with the limit in error_details. That is exactly the extra context this dimension rewards.

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?

Every sentence earns its place: purpose first, then the required id, then the fixed-org constraint, then the permission and seat-limit edge cases, then the preview gate. There is no filler and the constraints most likely to cause a wrong call are front-loaded.

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 three-parameter mutation with no output schema, the definition covers the safety profile (via annotations), the default dry-run behavior, the authorization limits, and the one foreseeable failure mode with its code and remedy. An agent has everything needed to call it correctly and to explain a refusal.

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 each parameter already carries a description, including the confirm preview/write distinction, so the baseline is 3. The description reinforces the confirm semantics and clarifies that the organization id must not be passed, but it leaves idempotency_key to the schema entirely and adds no syntax beyond what is documented.

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 opens with a specific verb and resource: 'Re-enable a previously disabled organization member', plus the outcome ('so they can log in and use the platform again'). That scope makes it distinguishable from the sibling disable_user without opening either schema.

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?

It states the required identifier, an explicit prohibition ('never pass an organization id' because the org is fixed by context), two targeting exclusions (cannot act on a more privileged user or on your own account), and a precise refusal condition with error code and how to report it. That is when-to-use, when-refused and what to tell the user.

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