PingRelay MCP Server

status_page_components_get

Read-onlyIdempotent

Get a non-deleted status page's ordered sections and grouped monitor components, uptime-history options, subscription/event visibility, colors, and font in the authenticated organization. Excludes deleted components/monitors and applies API theme defaults. Component Status is the stored numeric monitor status: 0 not set, 1 online, 2 down, 3 paused, 4 maintenance; it is not recalculated from paused flags or maintenance windows.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "statusPageExternalId": "<statusPageExternalId>"
    },
    "name": "status_page_components_get"
  }
}

Input Schema

Name	Required	Description	Default
`statusPageExternalId`	Yes	External status-page GUID returned as Id by StatusPageList.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds meaningful context beyond those annotations: it excludes deleted components/monitors, applies API theme defaults, and explains that Component Status is a stored numeric value (0-4) not recalculated from paused flags or maintenance windows. These details materially aid correct interpretation.

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?

The description is front-loaded with purpose and scope, followed by exclusions/defaults and then the Component Status enumeration. Every sentence adds useful information, and there is no filler or repetition. The density is justified by the amount of return-shape detail the description must carry.

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?

With no output schema, the description adequately covers the return contract: sections, grouped components, uptime-history options, subscription/event visibility, colors, font, exclusions, defaults, and status-code semantics. For a one-parameter read-only tool, this is complete enough for an agent to invoke and interpret the result correctly.

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 the sole parameter statusPageExternalId is already documented in the schema as the UUID returned by StatusPageList. The description does not add any further parameter-level meaning, such as validation rules or lookup behavior, so the schema carries the parameter semantics.

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?

The description states a specific verb and resource: 'Get a non-deleted status page's ordered sections and grouped monitor components, uptime-history options, subscription/event visibility, colors, and font.' This clearly distinguishes the tool from siblings like status_page_get and status_page_list, which do not focus on component/section layout. The scope is also constrained to the authenticated organization.

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

Usage Guidelines3/5

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

Usage is implied: call this to retrieve component and section configuration for a known status page. However, the description does not explicitly say when to choose this over status_page_get, status_page_list, or other status-page siblings, nor does it state when not to use it. The agent must infer the selection context.

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

All PingRelay MCP Server tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?