N-central MCP Server

search_organizations

Read-only

Find service organizations, customers, sites, or organizational units by name or filters. Use pagination and sorting to retrieve bounded results.

Instructions

Find service organizations, customers, sites, or organization units by human name or bounded filtering and pagination. Customer-scoped site listing is PREVIEW and may change.

Input Schema

TableJSON Schema

Name	Required	Description
`all`	No	Fetch bounded pages, up to 20 pages or 10,000 records.
`name`	No	Case-insensitive human-name search. Automatically scans bounded pages; do not combine with pageNumber or pageSize.
`select`	No	N-central FIQL/RSQL row filter.
`sortBy`	No	Field used to sort results.
`pageSize`	No	Page size from 1-1000; -1 is used only on documented operations.
`parentId`	No	Service-org parent for customers or customer parent for sites.
`nameMatch`	No	Human-name matching mode; requires name.
`sortOrder`	No	Sort direction.
`pageNumber`	No	Page number, starting at 1.
`organizationType`	Yes	Organization kind to search.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.0.0Sep 18, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only safety profile is covered. The description adds useful behavioral context by noting bounded filtering/pagination and flagging that customer-scoped site listing is PREVIEW and may change. This goes 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 two concise sentences with no filler. It front-loads the core purpose immediately and adds the preview caveat as a necessary second sentence.

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?

With a rich output schema, full parameter documentation, and annotations covering safety, the description is largely sufficient. It covers entity types and search modes, and the preview caveat addresses a key stability concern. A small gap is the lack of explicit sibling-tool routing, but that is not essential given the schema richness.

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?

Schema description coverage is 100%, so the baseline applies. The description adds high-level context like 'human name' and 'bounded filtering and pagination,' but the individual parameter semantics are already fully documented 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?

The description clearly states the tool finds service organizations, customers, sites, and organization units by human name or bounded filtering and pagination. This is a specific verb plus resource, though it does not explicitly differentiate itself from sibling tools like search_devices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage contexts: name-based search versus bounded filtering/pagination, and warns that customer-scoped site listing is PREVIEW. However, it does not explicitly say when to prefer this tool over search_devices or other siblings, nor does it mention exclusions.

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

Deploy Server