Skip to main content
Glama

mcp-uptimerobot__list-third-party-service-incidents

Read-onlyIdempotent

List incidents reported by the providers of the third-party services this account tracks, newest first. Pass monitorId to see one third-party service only. Open one with get-third-party-service-incident and see who was notified with get-third-party-service-incident-activity-log, passing its monitorId and id. These incident IDs do not work with get-incident-details or get-incident-activity-log. Through Royally: its server marks it read-only, so it runs straight away.

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": "mcp-uptimerobot__list-third-party-service-incidents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return per page (default: 10, max: 100)
cursorNoPagination cursor for next page
site_idNoSite to run this tool on: 0b6d9b21-ca64-4476-bc68-d1cd935ca7cb (https://mcp.uptimerobot.com/mcp)
monitorIdNoOnly incidents of this third-party service

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond that with the result ordering ("newest first"), the fact that incident IDs live in a separate namespace from regular incident IDs, and that it executes without a confirmation step ("runs straight away"). It says nothing about pagination behavior, but cursor/limit are documented in the schema.

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?

Front-loaded with the core purpose, then escalation path, then the ID-namespace caveat — a logical order with no filler. The closing sentence about the server marking it read-only is slightly awkwardly phrased but still carries the useful no-confirmation detail.

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

Completeness5/5

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

For a read-only list tool with full schema coverage and no output schema, the description covers scope, ordering, filtering, pagination-adjacent params (via schema), follow-up tools, and the ID-compatibility trap. An agent has everything needed to call it and chain correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description reinforces monitorId's meaning ("one third-party service only") and ties it to the follow-up calls that also take monitorId and id, but adds no format or constraint detail beyond the schema.

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

Purpose5/5

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

States a specific verb and resource ("List incidents reported by the providers of the third-party services this account tracks") plus ordering ("newest first"), which separates it cleanly from the sibling list-incidents tool covering first-party incidents.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: pass monitorId to narrow to one service, use get-third-party-service-incident to open one, use get-third-party-service-incident-activity-log for notified parties. It also adds an explicit negative rule — these IDs do not work with get-incident-details or get-incident-activity-log — which prevents a likely wrong-sibling call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources