Pingstack

List notification groups

list_notification_groups

Read-onlyIdempotent

List the account's notification groups, the recipients a check alerts when it fails or recovers, oldest first, 20 per page. Each item has the group id, name, user_ids (account members alerted directly), roster_ids (on-call rosters), check_count, delivery_configured (true when the group has at least one channel, member or roster) and channels_awaiting_confirmation. Channel addresses and delivery credentials aren't included. next_cursor is null on the last page. channels_awaiting_confirmation counts email channels that get no alerts until someone at the address confirms it in the app's confirmation email.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_notification_groups"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Items per page, 1 to 100. Defaults to 20.
`cursor`	No	next_cursor from the previous page. Omit for the first page; next_cursor is null on the last.

Output Schema

Name	Required	Description	Default
`items`	Yes
`next_cursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 10, 2026

addedOutput schema / properties / items / items / properties / check_count
```
Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}
```

addedOutput schema / properties / items / items / properties / roster_ids

Added value: +{
+  "items": {
+    "maxLength": 100,
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / items / items / properties / user_ids

Added value: +{
+  "items": {
+    "maxLength": 100,
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / items / items / required

Previous value: -[
-  "id",
-  "name",
-  "delivery_configured",
-  "channels_awaiting_confirmation"
-]New value: +[
+  "id",
+  "name",
+  "delivery_configured",
+  "channels_awaiting_confirmation",
+  "user_ids",
+  "roster_ids",
+  "check_count"
+]

AddedNov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, yet the description still adds real value: page ordering and size, the null-terminated next_cursor contract, an explicit exclusion list (channel addresses and delivery credentials are omitted), and the meaning of delivery_configured and channels_awaiting_confirmation. That is exactly the beyond-annotations context an agent needs to interpret results without being surprised by missing secrets.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose, scope, and page contract are front-loaded in the first sentence, and the field inventory follows logically. It is slightly dense — the trailing sentence re-explains channels_awaiting_confirmation after it already appeared in the field list — but no sentence is pure 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?

An output schema exists, so return values did not need spelling out, yet the description documents the key fields and their semantics anyway, including the two non-obvious booleans and the intentionally omitted sensitive fields. Combined with annotations covering the safety profile, an agent has everything required to call and interpret this 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 both limit and cursor are already documented and the baseline would be 3. The description adds information the schema does not carry — result ordering ("oldest first") and the fact that next_cursor is null on the last page — which materially affects how an agent drives the cursor loop.

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?

"List the account's notification groups" gives a specific verb plus resource, and the appositive "the recipients a check alerts when it fails or recovers" defines the resource precisely. The scope (account-wide, oldest first, paginated) and the enumerated item fields make it trivially distinguishable from create/update/delete/assign_notification_group siblings.

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 makes the enumeration context clear (account's groups, oldest first, paged via next_cursor) and implicitly steers mutation intents to the create/update/delete siblings by never framing this as an edit. It stops short of naming an alternative or stating when-not to use it, so it falls one step below fully explicit routing.

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

All Pingstack tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?