Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List users

nextcloud_list_users
Read-onlyIdempotent

Lists Nextcloud account IDs with optional search filtering and pagination controls, enabling user lookup and directory browsing.

Instructions

List account ids, optionally matching a search string.

GET /ocs/v2.php/cloud/users

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
searchNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this as read-only, idempotent, open-world, and non-destructive. The description adds the GET endpoint and clarifies that the result is account ids, but it does not add much beyond that, such as pagination behavior or search matching rules.

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?

The description is two short pieces with no wasted wording: the core purpose is front-loaded and the endpoint follows immediately. It is appropriately sized for a simple list operation.

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 tool has an output schema and rich annotations, so return values and safety behavior do not need to be repeated. However, with three parameters at 0% schema description coverage, the description should clarify what search matches and how limit/offset pagination works, which it does not.

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. It explains that search optionally matches a string, but it does not document limit or offset, leaving the pagination semantics entirely to parameter names and defaults.

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 has a specific verb and resource: list account ids, with an optional search filter. It clearly distinguishes listing users from user-detail tools, but it does not explicitly differentiate itself from sibling list tools such as list_groups or list_participants.

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?

The description implies browsing or searching users but gives no explicit guidance on when to use this tool instead of get_user, get_user_info, or other list tools. It also does not state prerequisites or when-not-to-use conditions.

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