Skip to main content
Glama
UptimeScout MCP server

UptimeScout MCP server

Official
by jsonscraper

uptimescout_services

Read-onlyIdempotent

Search the service catalog and retrieve regional availability observations, statuses, and historical uptime data for selected services, categories, regions, and time windows.

Instructions

Search the service catalog and get service availability observations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "uptimescout_services"
  }
}

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
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.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds nothing beyond them: it does not say what an observation contains, whether catalog search and observation retrieval happen in one call, or how limit/offset pagination behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no waste, which is good, but the brevity comes at the cost of substance rather than being earned economy. It is front-loaded but under-specified for a nine-parameter 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, zero-required tool that apparently merges catalog search with availability observations, the description is far too thin. With no output schema, the description needed to explain what an observation is and how the search parameters combine, and it does neither.

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%; lang, hours, and services are documented in the schema, but q, service, category, region, limit, and offset are not. The description contributes no parameter meaning at all, leaving unresolved whether q, service, services, and category are ANDed or mutually exclusive.

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 description names two actions, "search the service catalog" and "get service availability observations," giving a verb and a resource. However, "observations" is never defined, and nothing distinguishes this from siblings like uptimescout_status, uptimescout_history, or uptimescout_statuses, which plausibly overlap.

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 stated prerequisites, and no routing to alternatives among the six sibling tools. An agent has to guess whether this is the search entry point or an observation-fetching tool.

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