Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Enable user

nextcloud_enable_user
Idempotent

Re-enable a disabled Nextcloud user account by user ID. Use it to restore access for a specific user who has been deactivated.

Instructions

Enable one disabled account.

PUT /ocs/v2.php/cloud/users/{user_id}/enable

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": {
      "user_id": "<user_id>"
    },
    "name": "nextcloud_enable_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare it is a non-destructive, idempotent, open-world write, so the safety profile is covered. The description adds the target state ('disabled account') and the raw PUT endpoint, but omits permission requirements and what happens on a non-existent or already-enabled user.

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?

One front-loaded sentence plus the endpoint line; nothing is padded. The raw path is mildly redundant with the title but useful for agents reasoning about the API surface.

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 one-parameter, idempotent state-toggle with annotations covering safety and no output schema, the definition gives enough to call it correctly. Missing pieces — admin permission requirement and failure modes — are minor for this complexity.

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 description coverage is 0% for the single parameter, so the description carries the burden — and it partly does by showing {user_id} embedded in the request path, indicating it identifies an existing account rather than a name or email. It still doesn't state the expected ID format.

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?

States a specific verb and resource — 'Enable one disabled account' — which is directly distinguishable from the sibling nextcloud_disable_user and from nextcloud_enable_app. The scope qualifier ('one disabled') makes the intent unambiguous, though it doesn't explicitly name the inverse tool.

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?

Usage is only implied: the word 'disabled' signals the precondition, but the description never states when to reach for this versus nextcloud_disable_user, nextcloud_update_user, or nextcloud_create_user, nor any prerequisite such as admin rights.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools