nc-mcp-server

create_group

Create a new Nextcloud group by specifying an immutable group ID and optional display name, then add users with update_user. Requires admin rights.

Instructions

Create a new group. Requires admin rights (or delegated user administration).

Add users to it with update_user (its "groups" field).

Args: group_id: The group ID, used by the other tools to refer to it. Cannot be changed later. display_name: Name shown in the web interface. Defaults to the ID.

Returns: Confirmation message.

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": {
      "group_id": "<group_id>"
    },
    "name": "create_group"
  }
}

Input Schema

Name	Required	Description	Default
`group_id`	Yes
`display_name`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.9.0Oct 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations confirm a non-read-only, non-idempotent, non-destructive write. The description adds valuable traits beyond them: the admin-permission requirement, the immutability of group_id, and the display_name default. It does not discuss idempotency behavior or error modes, but the added context is meaningful.

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?

Front-loaded purpose, then permissions, then workflow, then structured Args. Dense with no filler sentences, and each line earns its place.

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?

An output schema already exists, so the brief 'Returns: Confirmation message' is sufficient. Combined with permissions, parameter semantics, and the follow-up path, an agent has everything needed to call this correctly.

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%, so the description must carry the load, and it does: group_id is explained as the persistent reference key that cannot change, and display_name as the UI name defaulting to the ID. Both parameters receive semantics beyond the bare schema types.

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?

States a specific verb and resource ('Create a new group') and distinguishes itself from siblings like list_groups, delete_group, and list_group_members without ambiguity. The follow-up note pointing to update_user adds scope context.

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?

Gives a clear precondition ('Requires admin rights (or delegated user administration)') and a concrete follow-up workflow (add users via update_user's groups field). It does not explicitly contrast against alternative creation paths, but the when-to-use context is solid.

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

Deploy Server