Skip to main content
Glama
Sign In

InfraNest

by io.infranest
OverviewDiscussionsAdmin

List status pages

list_status_pages
Read-onlyIdempotent

Every status page in your organization with its component and subscriber counts, how many components are operational or degraded, which are down, and the page’s 90-day uptime. component_feeds says what feeds each component and what it shows now (status). last_post is what the page last told visitors: an incident update (with its status, and automatic when no person posted it) or an announcement (with its title), whichever is newer, or null. What your customers are being shown right now.

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
organization_idNoThe organization to read. Leave it out when the token reaches only one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world. The description adds substantial return-value context: what fields are included, the meaning of `component_feeds`, and the `last_post` logic including null and automatic cases. It does not mention pagination, ordering, or error behavior, but the output semantics are unusually well explained.

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?

The description is front-loaded around the main resource and then explains key returned fields efficiently. The closing sentence is somewhat redundant but still reinforces the customer-facing purpose without excessive waste.

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?

Given the absence of an output schema, the description carries a lot of the return-value burden and does so well. It is complete enough for an agent to understand the tool's output, though it omits pagination, ordering, and explicit sibling differentiation.

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 description coverage is 100% and the single optional `organization_id` parameter is already documented in the schema. The description adds only the general phrase 'in your organization' and does not provide additional parameter-specific semantics beyond the schema.

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 clearly establishes the resource and scope: every status page in the organization, including component/subscriber counts, status breakdowns, uptime, feeds, and last visitor-facing post. It does not explicitly contrast this with sibling tools like status_overview or status_across_organizations, but the core purpose is clear.

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?

The description focuses entirely on what the tool returns, not when to use it. There is no explicit guidance on choosing it over status_overview, status_across_organizations, or uptime_report, and no prerequisites or exclusions are stated.

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

All InfraNest toolsInspect
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