nextcloud-agent

List groups

nextcloud_list_groups

Read-onlyIdempotent

List Nextcloud group IDs and optionally filter by a search string to identify groups for user, sharing, or permission management.

Instructions

List group ids, optionally matching a search string.

GET /ocs/v2.php/cloud/groups

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nextcloud_list_groups"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`search`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.0.0Nov 7, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the underlying OCS endpoint path, and says nothing about pagination, result ordering, or what happens when limit is exceeded — the behaviors an agent would actually need.

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?

The core purpose is front-loaded in a single short sentence with no filler. The trailing HTTP endpoint is mildly useful for orientation but is not something the agent acts on, so it is slight padding rather than a flaw.

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?

The presence of an output schema removes the need to describe return values, and the tool is simple with two optional parameters. However, for a list tool, the absence of any statement about the limit's cap or truncation behavior leaves a real gap for an agent that may need to page through many groups.

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 0%, so the description must carry parameter meaning, and it only clarifies that 'search' matches a search string. The 'limit' parameter — including its default of 100, any maximum, and whether it paginates — is left entirely unexplained in both schema and description.

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?

The description states a specific verb and resource ('List group ids') and adds the optional search behavior, which is enough to distinguish it from nextcloud_list_group_members or nextcloud_create_group. It does not explicitly name a sibling, but the resource is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus nextcloud_list_group_members or nextcloud_get_user's group info, and no prerequisites or exclusions are given. The word 'optionally' hints that search is not required, but that is the extent of the usage guidance.

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

Deploy Server