N-central MCP Server

list_active_issues

Read-only

Retrieve active monitoring issues for a customer or site. Filter, sort, and paginate results, with compact or full detail as needed.

Instructions

List current active monitoring issues for a customer or site (service-org scope is unsupported), with bounded pagination and a compact default projection. Use detailLevel=full only when complete upstream records are required.

Input Schema

TableJSON Schema

Name	Required	Description
`all`	No	Fetch bounded pages, up to 20 pages or 10,000 records.
`select`	No	N-central FIQL/RSQL row filter.
`sortBy`	No	Field used to sort results.
`pageSize`	No	Positive active-issue page size from 1-1000; defaults to 10 when omitted.
`orgUnitId`	Yes	Organization unit identifier.
`sortOrder`	No	Sort direction.
`pageNumber`	No	Page number, starting at 1.
`detailLevel`	No	compact (default) removes the verbose _extra object; full returns complete issue records.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv3.0.0Sep 18, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / all

Added value: +{
+  "description": "Fetch bounded pages, up to 20 pages or 10,000 records.",
+  "type": "boolean"
+}

addedInput schema / properties / detailLevel

Added value: +{
+  "description": "compact (default) removes the verbose _extra object; full returns complete issue records.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}

removedInput schema / properties / format

Removed value: -{
-  "description": "Output format: \"csv\" or \"json\". Default varies by tool — list_* default to json; report_* default to csv.",
-  "enum": [
-    "csv",
-    "json"
-  ],
-  "type": "string"
-}

addedInput schema / properties / orgUnitId / anyOf

Added value: +[
+  {
+    "description": "Organization unit identifier.",
+    "type": "string"
+  },
+  {
+    "description": "Organization unit identifier.",
+    "type": "number"
+  }
+]

changedInput schema / properties / orgUnitId / description

Previous value: -"The organization unit ID"New value: +"Organization unit identifier."

removedInput schema / properties / orgUnitId / type
```
Removed value: -"number"
```

addedInput schema / properties / pageNumber

Added value: +{
+  "description": "Page number, starting at 1.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / pageSize

Added value: +{
+  "description": "Positive active-issue page size from 1-1000; defaults to 10 when omitted.",
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / select

Added value: +{
+  "description": "N-central FIQL/RSQL row filter.",
+  "type": "string"
+}

addedInput schema / properties / sortBy

Added value: +{
+  "description": "Field used to sort results.",
+  "type": "string"
+}

addedInput schema / properties / sortOrder

Added value: +{
+  "description": "Sort direction.",
+  "enum": [
+    "asc",
+    "ascending",
+    "natural",
+    "desc",
+    "descending",
+    "reverse"
+  ],
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {},
+    "meta": {
+      "additionalProperties": false,
+      "properties": {
+        "errors": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "code": {
+                "type": "string"
+              },
+              "component": {
+                "type": "string"
+              },
+              "message": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "component",
+              "code",
+              "message"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "operations": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "page": {},
+        "partial": {
+          "type": "boolean"
+        },
+        "truncated": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "operations",
+        "partial",
+        "errors",
+        "page",
+        "truncated"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "type": "object"
+}

First observedv2.1.0Jun 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the read-only and non-destructive nature. The description adds meaningful behavioral context: bounded pagination, a compact default projection, and the service-org unsupported constraint, all of which are not inferable from annotations alone.

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, no filler. The core purpose and scope are front-loaded, and the detailLevel guidance is placed where it matters most. Every clause carries signal.

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 moderately complex 8-parameter tool with an output schema, the description conveys the essential non-obvious details: scope limitations, pagination bounds, default projection, and when to request full records. The output schema handles return-value specifics, so nothing critical is missing.

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 the baseline is 3, but the description adds value by explaining the trade-off between compact and full detailLevel and stating the default behavior. This gives the agent actionable selection guidance beyond the schema's enum descriptions.

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 names a specific verb and resource: 'List current active monitoring issues'. It also narrows scope to customer or site and explicitly excludes service-org scope, which clearly distinguishes it from sibling tools like list_job_statuses or 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 Guidelines4/5

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

It gives clear context: active issues for a customer/site, service-org unsupported, and provides a decision rule for detailLevel ('use full only when complete upstream records are required'). It does not name alternative tools for comparison, but the scope constraints effectively guide when to use this tool.

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

Deploy Server