nc-mcp-server

list_forms

Read-onlyIdempotent

List Nextcloud forms you own or that are shared with you, with optional ownership filtering. Returns form summaries including id, title, state, and permissions for quick overview.

Instructions

List forms visible to the current user.

Args: ownership: Filter. One of: "owned" (forms I created), "shared" (forms shared with me). Omit to get both — the Nextcloud endpoint takes one filter at a time, so this tool calls it twice and merges the results when omitted.

Returns: JSON array of form summaries. Each entry includes id, hash, title, state (0=active, 1=closed, 2=archived), permissions, and metadata. Call get_form(id) for full details including questions.

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

Input Schema

Name	Required	Description	Default
`ownership`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, but the description adds genuine behavioral insight: the underlying endpoint takes one filter at a time, so omitting ownership triggers two API calls and a merge. It also documents the state enum values (0=active, 1=closed, 2=archived), going beyond the annotations without contradicting them.

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 compact and front-loaded: purpose first, then parameter explanation, then return shape, then a pointer to the sibling tool. Every sentence carries useful information with no filler or repetition of the schema.

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?

The tool is simple (one optional parameter, read-only) and the description covers the parameter behavior, the return summary fields, and the alternative for full details. Since an output schema exists, the return-format summary is enough; the only minor omission is ordering/pagination, but nothing suggests those apply to this endpoint.

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 coverage is 0% and the schema only declares the ownership property as string/null. The description fully compensates by listing the exact allowed values ('owned' and 'shared') and explaining the default/omission behavior, which is critical for correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'List forms visible to the current user', a specific verb + resource with a scope qualifier. It then distinguishes itself from get_form by noting this returns summaries and pointing to get_form for full details including questions, so an agent can tell it apart from sibling tools.

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?

It explains the ownership filter's two values and what happens when omitted (two-call merge), and explicitly routes to get_form when full details are needed. It doesn't spell out 'when not to use' but the alternative is named with the condition, which is sufficient guidance.

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

Deploy Server