nc-mcp-server

list_flows

Read-onlyIdempotent

Retrieve Nextcloud Flow rules (automated file workflows) for user or global scope, with pagination via limit and offset. Returns JSON with flows and pagination.

Instructions

List Nextcloud Flow rules (workflows that act on files automatically).

Args: scope: "user" for the current user's own flows, or "global" for the admin flows that apply to everyone (admin only). limit: Maximum number of flows to return (1-200, default 50). offset: Number of flows to skip for pagination (default 0).

Returns: JSON with "data" (flows with id, name, operation_class, operation_config, entity, events and checks, each check having class, operator and value) and "pagination" (count, offset, limit, has_more).

Input Schema

TableJSON Schema

Name	Required	Default
`limit`	No
`scope`	No	user
`offset`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.9.0Oct 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish the safe read-only, idempotent profile, so the description only needs to add context — and it does: admin-only access for scope='global' and the presence of a has_more pagination flag. It does not discuss rate limits or ordering, which is a minor residual gap.

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-loads the one-line purpose, then uses labeled Args/Returns blocks so an agent can scan directly to the needed detail. Every sentence carries information; nothing is filler.

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?

For a three-parameter, zero-required listing tool with annotations covering the safety profile, the description supplies purpose, per-parameter semantics, authorization caveats, and pagination behavior. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does: scope's enum-like values with their authorization difference, limit's range (1-200) and default (50), and offset's pagination meaning with default (0). This is far richer than the bare typed properties in the 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?

States a specific verb and resource ('List Nextcloud Flow rules') and even glosses what a Flow is ('workflows that act on files automatically'). It does not differentiate itself from siblings like create_flow, update_flow, delete_flow, or get_flow_options, but the read-only listing intent is unmistakable.

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?

The scope argument documentation gives real selection guidance: 'user' for one's own flows vs 'global' for admin flows applying to everyone, with an explicit admin-only restriction. It does not route to sibling tools, but the when-to-use context is clear.

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

Deploy Server