Skip to main content
Glama

Disable an app user and end all their sessions

app_users_disable

Disabled.

POST /api/v1/app-users/{id}/disable

For multi-space accounts, call auth_verify, ask the user which space to use, and pass targetSpaceId.

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": {
      "id": "<id>"
    },
    "name": "app_users_disable"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
targetSpaceIdNoBusabase space id. Call auth_verify first and ask the user which space to use when more than one is returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is mostly covered. The description contributes the cross-cutting prerequisite (auth_verify plus space selection), but the body never states that all sessions are terminated (that fact lives only in the title), nor whether the action is reversible via app_users_enable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short and there is no padding, but the lead line "Disabled." is a broken fragment occupying the most valuable position instead of stating purpose. The endpoint line and the space-selection sentence are the only substantive content.

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 mutation tool with no output schema and only partial schema coverage, the description should disclose the side effect of ending all sessions, reversibility, and any required permissions. It omits all of these and does not help the agent distinguish disabling from the adjacent app_users_delete operation.

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 50%, and the uncovered half is the required `id` parameter, which the description never explains as the app-user identifier. The only parameter the description discusses, targetSpaceId, merely restates the schema's own property description word for word, adding no new meaning.

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

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description body opens with the dangling fragment "Disabled." rather than stating a verb and resource; the actual purpose is only recoverable from the endpoint line `POST /api/v1/app-users/{id}/disable` and the title. It never names the sibling it differs from (app_users_delete, app_users_enable), so the agent must infer the distinction.

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

Usage Guidelines3/5

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

Useful procedural guidance is given for the multi-space case: call auth_verify, ask the user which space, then pass targetSpaceId. However, there is no guidance on when to use this instead of app_users_delete or when to prefer it over leaving the user enabled, which is the more consequential selection decision.

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.