nc-mcp-server

list_collectives

Read-onlyIdempotent

Retrieve a paginated list of shared knowledge bases (collectives) the current user can access, with names, emojis, and permissions. Use limit and offset to control the result set.

Instructions

List collectives the current user has access to.

Collectives are shared knowledge bases with wiki-style pages.

Args: limit: Maximum number of collectives to return (1-200, default 50). offset: Number of collectives to skip for pagination (default 0).

Returns: JSON with "data" (list of collectives with id, name, emoji, permissions) and "pagination" (count, offset, limit, has_more).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`offset`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already mark this as safe/read-only/idempotent. The description adds useful behavioral detail beyond that: it reveals the return shape (data list with id, name, emoji, permissions) and pagination fields, making the response predictable without contradicting the annotations.

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 with the essential purpose, followed by a brief domain definition and clearly separated Args/Returns sections. Every sentence adds value; there is no 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 simple paginated listing tool, the description covers the operation, param semantics, and return structure completely. The output schema exists, so the written return format is a bonus rather than a necessity.

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?

The schema provides only types and defaults, while the description fully explains both parameters: limit's range (1-200) and default, and offset's pagination purpose and default. This fully compensates for the 0% schema description coverage.

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?

States a specific verb ('list') and resource ('collectives'), scoped by accessibility ('current user has access to'). Defining collectives as 'shared knowledge bases with wiki-style pages' removes ambiguity and helps distinguish this from page-level operations like get_collective_pages.

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 description gives clear context for when to call it: to retrieve a paginated list of collectives accessible to the current user. It doesn't explicitly name alternatives or exclusions, but it is the canonical listing operation among the sibling tools and its scoping 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