Skip to main content
Glama
UptimeScout MCP server

UptimeScout MCP server

Official
by jsonscraper

uptimescout_status

Read-onlyIdempotent

Retrieves a service's availability status with observation time and explicit freshness, so clients can assess uptime without triggering new data collection.

Instructions

Get a service status with observation time and explicit freshness.

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": {
      "service": "<service>"
    },
    "name": "uptimescout_status"
  }
}

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
serviceYes
categoryNo
servicesNoComma-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.7/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds a useful signal that results carry observation time and explicit freshness markers, but says nothing about pagination behavior, region independence, or the history-window slotting that the `hours` parameter implies.

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 front-loaded sentence with zero filler. It is efficient, though the terseness tips into under-specification rather than crispness.

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 9-parameter tool with no output schema and 33% parameter documentation, one sentence is far too little. An agent cannot tell what fields come back, how `hours` affects the response, or how to disambiguate from sibling status/history tools.

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

Parameters2/5

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

With 9 parameters and only 33% schema description coverage, the description must compensate and does not. It says nothing about `q`, `limit`, `offset`, `region`, `category`, or the confusing relationship between `service` and `services` (max 100 IDs).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource is identifiable ("Get a service status"), and "observation time and explicit freshness" hints at the returned fields. But it never distinguishes this from siblings like uptimescout_statuses or uptimescout_history, and it doesn't resolve the ambiguity of a required single `service` parameter coexisting with a `services` list parameter.

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 when-to-use guidance, no exclusions, and no named alternative despite six sibling tools whose names overlap heavily (status vs statuses, history, summary). The agent must guess which status tool to call.

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