Skip to main content
Glama

Disable user

disable_user
DestructiveIdempotent

Disable an organization member's access to this organization: until they are enabled again they can open nothing in it (their sign-in and their other organizations are not affected). Reversible — the user can be re-enabled from the web application. 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": "disable_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional reason for disabling the user (stored for audit purposes).
confirmNoSet true to perform the action. Omit or false returns a preview only — nothing is written.
org_user_idYesId of the OrganizationUser record to disable (not the Firebase userId).
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. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the destructive/idempotent annotations, the description discloses the actual effect ('they can open nothing in it'), the unaffected surface (sign-in, other orgs), reversibility, and the preview-first behavior. That is real added value; it stops short of describing what the preview returns or what happens to in-flight sessions/assignments.

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?

Front-loaded with the action and its scope, then reversibility, then the preview rule — a sensible order with no filler. The parenthetical about sign-in and other organizations is slightly cramped but earns its place.

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

Completeness4/5

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

For a 4-parameter mutation with no output schema, the definition covers effect, reversibility, and the dry-run gate, which is what an agent needs to call it correctly. The one residual gap is what the preview response looks like, though annotations and the schema carry most of the rest.

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%, so all four parameters are documented in the schema itself. The description only echoes the confirm semantics already present in the schema and adds nothing about org_user_id, reason, or idempotency_key beyond it — baseline 3 applies.

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?

Precise verb plus resource with an explicit blast radius: it disables an org member's access to *this* organization and explicitly excludes sign-in and other organizations. That scoping distinguishes it from a global account action, though it never names the sibling tools (enable_user, remove_user) it sits beside.

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?

The confirm=true dry-run/execute contract is stated plainly, which tells the agent how to call it safely. What's missing is the when-to-use distinction against remove_user (permanent removal) or enable_user — the reader must infer that from the name and description.

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