Skip to main content
Glama

status_page_list

Read-onlyIdempotent

List all non-deleted status pages in the authenticated organization with host/domain, basic metadata, and section summaries. No pagination or result limit. Use StatusPageComponentsGet for ordered monitor components, visibility settings, and theme configuration.

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": "status_page_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, but the description still adds real value: it discloses the deleted-record filter and that results are unbounded ("No pagination or result limit"), which matters for an agent planning around response size. It does not describe ordering or behavior on an empty organization.

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 resource and scope come first, the result-shape note second, and the sibling routing last — a sensible front-loaded order.

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 zero-argument, read-only list tool with no output schema, the description supplies everything an agent needs: what is included, that deleted pages are excluded, that results are not paginated, and where to go for deeper status page details. No annotation or schema data is merely restated.

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?

The tool takes no parameters, so the baseline is 4 and the description correctly spends no space on argument semantics. The added note that there is no pagination fills the only parameter-adjacent gap an agent might wonder about.

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 all non-deleted status pages") plus the scope ("in the authenticated organization") and the returned content (host/domain, metadata, section summaries). It also names the sibling it is not for component-level data, so an agent can distinguish it without opening schemas.

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 'non-deleted, whole-organization' framing and the explicit routing of components/visibility/theme work to the components tool give clear usage context. It does not explicitly address when to use this versus status_page_get for a single page, which is the one remaining ambiguity.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources