Skip to main content
Glama
UptimeScout MCP server

UptimeScout MCP server

Official
by jsonscraper

uptimescout_history

Read-onlyIdempotent

Retrieve regional uptime aggregates for services by time window and resolution, including sample counts and effective start times, to analyze availability trends and flag unknown intervals.

Instructions

Read regional history: weighted time-slot aggregates at 3-minute, 5-minute, hourly and daily resolutions. Saved legacy aggregates keep their declared coarser resolution. Inspect resolution_seconds, samples, counts and effective_start; missing intervals are unknown.

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_history"
  }
}

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

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description adds genuine new context: resolution tiers, that saved legacy aggregates return at their coarser declared resolution, and critically that missing intervals mean unknown rather than zero. It does not discuss pagination behavior despite limit/offset params.

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?

Three dense sentences with the core capability front-loaded and no filler; the 'inspect resolution_seconds, samples, counts and effective_start' clause is compact and actionable. Slightly telegraphic phrasing, but nothing extraneous.

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

Completeness3/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, the description gives useful data-shape context (which fields to inspect, missing-interval semantics) but leaves most input parameters unexplained, so an agent could still mis-set region, service, or paging arguments.

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?

Schema description coverage is only 33% across 9 parameters, so the description needs to compensate and largely doesn't—q, limit, offset, region, service, category, and services are unaddressed. Only resolution is discussed, and even there hours/resolution_seconds semantics are mostly carried by the schema itself.

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?

'Read regional history: weighted time-slot aggregates' names a specific verb, resource, and data shape, which separates it from siblings like uptimescout_incidents or uptimescout_statuses. It doesn't explicitly contrast with the potentially overlapping uptimescout_stats, so it falls short of full sibling differentiation.

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 rather than stated: the tool is for regional historical aggregates across resolutions, and the note about legacy aggregates suggests when coarser data may come back. There is no explicit when-to-use/when-not guidance or named alternative for point-in-time versus historical queries.

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