Skip to main content
Glama
theonlytruebigmac

N-central MCP Server

list_all_users

Read-only

Retrieve a global list of all users in N-central. Supports pagination, filtering, and CSV export for spreadsheet-ready data.

Instructions

Retrieve a global list of all users in N-central (not scoped by org unit). Returns one page by default — set all: true to auto-paginate. Use format: "csv" for spreadsheet-ready output.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNumberNoPage number (starts at 1)
pageSizeNoNumber of items per page (max 200)
selectNoFilter expression (FIQL/RSQL predicate) — despite the "select" name, this filters rows, it does NOT pick fields. Syntax: `field==value`, join predicates with `;` for AND. Example: `soId==50` returns only the SO with that ID. Not all fields are queryable; unsupported ones error with "Field not found: X".
sortByNoField to sort results by
sortOrderNoSort order: ASC, asc, ascending, natural, desc, descending, reverse
allNoAuto-paginate: fetch every page and return the combined list. Ignores pageNumber/pageSize. Use for complete results; omit to return a single page (cheaper, safer for large environments).
formatNoOutput format: "csv" or "json". Default varies by tool — list_* default to json; report_* default to csv.
Behavior4/5

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

Annotations already declare the tool as read-only and non-destructive. The description adds value by explaining auto-pagination behavior and output format options (csv/json). No contradiction with 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?

Two sentences, front-loaded with purpose, followed by key usage details. No extraneous information; every sentence is necessary.

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 description lacks details about the return structure (e.g., fields in the user objects or CSV columns). Although it mentions output formats, without an output schema, the description should outline what is returned. This is a gap for a list tool.

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

Parameters3/5

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

Input schema coverage is 100% with descriptive parameter details. The description adds minor context (e.g., 'use format csv for spreadsheet-ready output'), but does not significantly enhance meaning beyond what the schema already provides.

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 clearly identifies the tool's action ('Retrieve') and resource ('global list of all users') and specifies it is not scoped by org unit. This distinguishes it from siblings like list_users (likely scoped) and report_all_users_by_so (a report).

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 explains default behavior (one page) and how to change it (all: true for auto-pagination, format: 'csv'). It does not explicitly state when not to use this tool or name alternatives, but the advantage of pagination vs. full list is implied.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/theonlytruebigmac/n-central-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server