Skip to main content
Glama
UptimeScout MCP server

UptimeScout MCP server

Official
by jsonscraper

uptimescout_stats

Read-onlyIdempotent

Calculate weighted observation ratios from sample counts and time-slot aggregates for services, using UTC-aligned history and region metadata; results are observations, not measured uptime.

Instructions

Calculate weighted observation ratios from sample counts, including weighted time-slot aggregates. Not measured uptime. Inspect effective_start for UTC-slot alignment.

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

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.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context by warning that results are not measured uptime and by pointing at the effective_start field for UTC-slot interpretation, but it does not explain the weighting method or what the response contains.

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 short, front-loaded sentences with no filler; the most important disambiguation ('Not measured uptime') comes early. It is tight to the point of being cryptic, but nothing is redundant.

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 statistical tool with no output schema and low schema coverage, the description leaves the weighting algorithm, response shape, and most parameter meanings unexplained. The single pointer to effective_start is not enough to make the tool callable with confidence.

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: q, service, services, category, region, limit and offset carry no documentation in either schema or description. The description offers no clarification of how service/services/category interact or how the hours window affects aggregation, so it fails to compensate for the coverage gap.

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 gives a specific verb and resource ('Calculate weighted observation ratios from sample counts') and explicitly carves out what it is not ('Not measured uptime'), which separates it from sibling tools that report actual uptime. The jargon 'weighted observation ratio' is not defined, so the agent knows the category but not the exact semantics of the number.

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?

'Not measured uptime' functions as an implicit guidance cue: use it for ratio/aggregate statistics rather than current status. However, no sibling is named and no explicit when-to-use versus when-to-use-something-else condition is stated, so the agent must infer routing.

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