nextcloud-agent

List apps

nextcloud_list_apps

Read-onlyIdempotent

List installed Nextcloud app IDs by status—enabled, disabled, or all—to audit or manage available applications.

Instructions

List installed app ids that are enabled, disabled, or all of them.

GET /ocs/v2.php/cloud/apps

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

Input Schema

Name	Required	Description	Default
`status`	No		enabled

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.0.0Nov 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the raw OCS endpoint path, and says nothing about pagination, result ordering, or the admin-level permission typically required to list apps in Nextcloud.

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 states the resource and the filter dimension, with no padding. The trailing 'GET /ocs/v2.php/cloud/apps' line is marginally useful implementation detail but not agent-actionable information.

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 single-optional-parameter read tool with an output schema and rich annotations, almost everything an agent needs is present. The remaining gap is the permission/scope expectation for listing apps, which is often admin-restricted in Nextcloud and is not mentioned anywhere.

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 meaning, and it does enumerate the three meaningful modes (enabled / disabled / all) that the enum exposes. It stops short of stating the default ('enabled') or that results are bare app ids rather than full app objects, so it is good but not complete.

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 ('List installed app ids') plus the scope of the filter (enabled, disabled, or all). This clearly separates it from nextcloud_get_app (single app) and nextcloud_enable_app / nextcloud_disable_app (mutations), though no sibling is named explicitly.

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: an agent can infer this is the enumeration tool for apps, and the phrase 'enabled, disabled, or all' hints that the status parameter controls scope. There is no explicit when-to-use statement, no mention that this is the discovery step before get_app/enable_app/disable_app, and no caveats about who may call it.

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

Deploy Server