Skip to main content
Glama
theonlytruebigmac

N-central MCP Server

list_users

Read-only

Retrieve users for a specific organization unit, with pagination, filtering, sorting, and export to CSV or JSON.

Instructions

Retrieve the list of users for a specific organization unit. Returns one page by default — set all: true to auto-paginate. Use format: "csv" for spreadsheet-ready output.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgUnitIdYesThe organization unit ID
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 readonly and non-destructive behavior. Description adds pagination behavior and format options, which are valuable beyond annotations. No contradiction.

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 core purpose, no wasted words. Every sentence provides actionable guidance.

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?

No output schema, but tool is simple. Covers key usage aspects (pagination, format, required org unit). Lacks explicit mention of returned fields, but sufficient for a list tool.

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 coverage is 100%, so baseline is 3. Description adds value by specifying default pagination (one page) and format relevance, which are not in schema. Reinforces usage of 'all' and 'format' parameters.

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?

The description clearly states 'Retrieve the list of users for a specific organization unit' with a specific verb and resource. It doesn't explicitly distinguish from sibling list_all_users, but the purpose is well-defined.

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?

Provides guidance on pagination (default one page vs auto-paginate with all: true) and output format (csv for spreadsheet), but doesn't discuss when to use list_users vs list_all_users.

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