Pingstack

List on-call rosters

list_rosters

Read-onlyIdempotent

List the account's on-call rosters, oldest first, 20 per page. Each item has the roster id, name and the user ids of its members. A roster is a named set of people that notification groups can alert together. There are no filters, and an account with no rosters returns an empty list. Rosters are created and edited in the app. next_cursor is null on the last page.

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_rosters"
  }
}

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.

AddedNov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavior: deterministic ordering, the empty-account case returning an empty list, and the pagination terminator semantics.

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?

Front-loaded with the action and scope, then the roster definition, then pagination notes. Slight redundancy: the default page size and the null next_cursor on the last page are each stated in both the description and the schema.

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 two-parameter, no-filter list tool with an output schema, everything an agent needs is present: ordering, page size, empty-set behavior, cursor termination, and where rosters are managed.

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 coverage is 100% and both parameters already document their ranges, defaults and cursor semantics. The description restates '20 per page' and the null next_cursor on the last page but adds no new syntax or edge cases beyond the schema.

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?

States a specific verb and resource ('List the account's on-call rosters') plus ordering ('oldest first') and page size, and defines what a roster is so the agent can tell it apart from notification groups and account members.

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?

Makes clear this is an unfiltered list ('There are no filters') and that mutation happens elsewhere ('Rosters are created and edited in the app'), steering the agent away from hunting for a create/update roster tool. It does not explicitly contrast with list_notification_groups, so it stops short of full alternative 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?