Skip to main content
Glama

Re-enable a disabled app user

app_users_enable

Enabled.

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

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_enable"
  }
}

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

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the POST endpoint is consistent with a state-mutating operation, so no contradiction. The description adds the multi-space prerequisite as real behavioral context, but says nothing about permissions required, idempotency, or what happens if the user is already enabled.

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?

It is short, but poorly structured: the one-word fragment "Enabled." leads and carries almost no information, followed by a raw URL, then the only genuinely useful instruction. The front-loaded content is the weakest part rather than the strongest.

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

Completeness3/5

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

For a two-parameter mutation with no output schema, the definition covers the space-selection workflow but leaves gaps an agent would care about: preconditions on the target user's state, permission requirements, and failure behavior. Adequate to attempt the call, not complete.

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 50%: targetSpaceId is already documented in the schema, and the description largely repeats that same instruction. The required 'id' parameter carries no explanation in either place, and the description does not clarify whether it is a user id or record id.

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

Purpose3/5

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

The body opens with the bare token "Enabled." and then a raw endpoint path, so the actual verb+resource (re-enable a disabled app user) is only reconstructed from the name, title and URL. It is decipherable but the description itself never states the action in a sentence, and it does not distinguish itself from app_users_disable.

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?

There is a concrete usage rule for the multi-space case: call auth_verify first and ask the user which space to use, then pass targetSpaceId. There is no guidance on the primary when-to-use condition (e.g. only when the user is currently disabled) or on when to prefer app_users_disable instead.

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.