Skip to main content
Glama
UptimeScout MCP server

UptimeScout MCP server

Official
by jsonscraper

uptimescout_statuses

Read-onlyIdempotent

Batch-retrieve service statuses for multiple services using comma-separated IDs, with optional region and history-window filters for availability monitoring.

Instructions

Get a batch of service statuses.

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": {
      "services": "<services>"
    },
    "name": "uptimescout_statuses"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
langNoLanguage of service descriptions; observation region is independent.
hoursNoHistory window. History aligns to UTC slots: 3 minutes through 1 hour, 5 minutes through 3 hours, 1 hour through 24 hours, and 1 day through 90 days.
limitNo
offsetNo
regionNo
serviceNo
categoryNo
servicesYesComma-separated service IDs (maximum 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.4
    • addedInput schema / properties / hours / description
      Added value: +"History window. History aligns to UTC slots: 3 minutes through 1 hour, 5 minutes through 3 hours, 1 hour through 24 hours, and 1 day through 90 days."
    • addedInput schema / properties / hours / examples
      Added value: +[
      +  1,
      +  24,
      +  720,
      +  2160
      +]
    • addedInput schema / properties / lang
      Added value: +{
      +  "description": "Language of service descriptions; observation region is independent.",
      +  "enum": [
      +    "en",
      +    "ar",
      +    "cs",
      +    "de",
      +    "es",
      +    "fi",
      +    "fr",
      +    "he",
      +    "it",
      +    "ja",
      +    "ko",
      +    "nl",
      +    "no",
      +    "pl",
      +    "pt",
      +    "ru",
      +    "sv",
      +    "tr",
      +    "uk",
      +    "zh"
      +  ],
      +  "type": "string"
      +}
  2. First observedv0.1.1

TDQS

C2.8/5.0
Behavior2/5

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

The annotations already establish read-only, idempotent, non-destructive behavior. Beyond those fields, the description adds only that retrieval is batched, with no context about status semantics or freshness, pagination, or how history and filters affect the result.

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 single sentence is front-loaded and contains no filler. Its brevity is efficient, although it is too terse to provide well-rounded guidance for a parameter-rich tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter tool with no output schema and low parameter coverage, one generic sentence is insufficient to support reliable selection and invocation. It leaves batch-versus-single usage, filter interactions, and result behavior unclear, though the required services parameter itself is documented in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, and the description explains none of the nine parameters or their interactions. In particular, q, limit, offset, region, service, and category lack schema descriptions without any compensating explanation in the description.

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 provides a clear verb ("Get"), resource ("service statuses"), and batch scope. It does not explicitly distinguish the operation from the singular uptimescout_status or other siblings.

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?

The word "batch" implies that the tool is intended for retrieving statuses for multiple services. There is no explicit guidance on when to choose it over uptimescout_status or any other sibling, nor any prerequisites or exclusions.

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