Skip to main content
Glama

Statuspage Multi Check

statuspage_multi_check
Read-onlyIdempotent

Check the live service status of several vendors at once, "are any of my providers down right now?". Takes a list of vendor names or Statuspage hostnames and returns one compact row each: status indicator, the vendor's status line, open incident count and degraded component count, plus a roll-up naming which are operational, which are degraded or in an outage, and which could not be reached. Use for dependency health sweeps, incident triage across a stack, and monitoring a set of upstream APIs in one call.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vendors": [
        "openai",
        "anthropic",
        "github",
        "cloudflare"
      ]
    },
    "name": "statuspage_multi_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendorsYesVendor names/keys, or bare Statuspage hostnames (anything containing a dot is treated as a host). 1-20 entries, e.g. ["openai", "anthropic", "github", "cloudflare"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 open-world, so safety is covered. The description adds real value beyond them by specifying the return shape per vendor (status indicator, status line, open incident count, degraded component count) and a roll-up that classifies vendors as operational, degraded/outage, or unreachable, which tells the agent how partial failures surface.

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?

Two sentences, front-loaded with the core action and intent question, followed by output shape and use cases. The 'Use for...' list is compact, though the opening quote-question is slightly decorative rather than strictly necessary.

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?

For a one-parameter, no-output-schema tool, the description covers action, input kind, return contents and failure mode ('could not be reached'), which is what an agent needs. Only minor gaps remain, such as behavior for unrecognized vendor names versus network failures and whether the roll-up is a separate field or prose.

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 schema already documents vendor names, hostname handling ('anything containing a dot is treated as a host'), and the 1-20 bound. The description restates 'vendor names or Statuspage hostnames' without adding format or resolution rules, so it neither compensates for nor extends the schema. Baseline 3 applies.

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 ('Check the live service status of several vendors at once') and immediately scopes it with a user-intent gloss ('are any of my providers down right now?'). The word 'several'/'at once' and the batch return shape implicitly separate it from the singular statuspage_check sibling.

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?

Names three concrete scenarios: dependency health sweeps, incident triage across a stack, and monitoring upstream APIs in one call. It does not explicitly say when to prefer statuspage_check for a single vendor or statuspage_incidents for incident detail, so the boundary with siblings is left to inference.

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.