Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List group members

nextcloud_list_group_members
Read-onlyIdempotent

List account IDs for a specified group to identify its members and support group-based access or user management.

Instructions

List the account ids in one group.

GET /ocs/v2.php/cloud/groups/{group_id}/users

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": "nextcloud_list_group_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and idempotency profile is fully covered structurally. The description adds essentially nothing beyond that: it restates the read operation and, at best, hints that returned values are account ids, which the output schema already specifies. It says nothing about behavior for a nonexistent group, permissions required, or result size.

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?

Two short lines with the purpose front-loaded and no filler. The endpoint line is marginally useful as routing context but is essentially restated structured information rather than earning its place as behavioral detail.

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?

Because an output schema exists, the description need not explain return values, and for a simple single-parameter read the definition is close to sufficient. Gaps remain around the identity format of group_id and error behavior for unknown groups, which are the main things an agent could get wrong when calling this.

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?

With schema description coverage at 0% and a single required group_id, the description does partially compensate by tying the parameter to "one group" and showing it as a path segment in the endpoint. However, it never clarifies whether group_id is a group name, display name, or internal id, nor any format constraints, leaving a real ambiguity for a 0%-coverage schema.

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 gives a specific verb and resource ("List the account ids in one group") plus the underlying endpoint, so an agent can tell this is a per-group membership read rather than a general user listing. It does not explicitly name the nearest siblings (nextcloud_list_users, nextcloud_list_groups, nextcloud_list_participants), so differentiation is implied by "in one group" rather than stated.

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 when-to-use or when-not-to-use guidance and no mention of alternatives such as nextcloud_list_users for a global list or nextcloud_list_participants for conversation members. The agent must infer selection criteria from the tool name and the phrase "in one group" alone.

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