Skip to main content
Glama

Status pages

list_status_pages
Read-only

The workspace's status pages: their address (/status/{slug}), the monitors they show with the names visitors see, and their named groups of monitors in order. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: it discloses the return shape (slug-based addresses, visitor-visible monitor names, ordered groups) and the trailing 'Free' signals there is no plan or billing gate on this endpoint. It does not state whether results are paginated, but with zero parameters the natural reading is a single complete listing.

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?

A single sentence that front-loads the resource and then enumerates its three components, with no redundant wording. The standalone 'Free.' fragment is terse but does carry information, though it reads as an afterthought appended to the list.

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 no output schema, the description carries the burden of describing return values, and it does so adequately by naming the three fields an agent will receive and their ordering. For a zero-parameter read tool this is close to complete; only listing breadth or pagination behavior is left unspecified.

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 there is nothing for the description to disambiguate. It correctly adds no parameter narrative, keeping the text focused on returned content.

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 enumerates exactly what the tool surfaces: status page addresses in the /status/{slug} form, the monitors each page displays under visitor-facing names, and their named monitor groups in order. The verb is implied by the name rather than stated, and no sibling is named for contrast, but the resource and its contents are unambiguous.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named — notably it never distinguishes itself from list_monitors or update_status_page_components. An agent must infer from the noun phrase alone that this is the read path for status page configuration.

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