Skip to main content
Glama

mcp-uptimerobot__get-incident-alerts

Read-onlyIdempotent

Read the alerts sent during an incident: a summary (counts by delivery status, the contacts involved, the most recent alert) followed by the newest page of sent alerts. Answers "were alerts sent, and to whom?" in one call even on an incident with thousands of notifications. Recipient values are shown in full only for identifier-shaped contact types (email, SMS, voice); every other type is "[REDACTED]". Through Royally: its server marks it read-only, so it runs straight away.

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": {
      "incidentId": "<incidentId>"
    },
    "name": "mcp-uptimerobot__get-incident-alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of sent alerts to return (1-200, default 50)
cursorNoPagination cursor for the next page of sent alerts
site_idNoSite to run this tool on: 0b6d9b21-ca64-4476-bc68-d1cd935ca7cb (https://mcp.uptimerobot.com/mcp)
incidentIdYesIncident ID (a BigInt value, passed as a numeric string)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive and closed-world profile, and the description reinforces this by saying it 'runs straight away'. More importantly it discloses genuinely non-obvious behavior the annotations cannot carry: recipient values are fully shown only for email/SMS/voice and redacted as '[REDACTED]' otherwise, and results are ordered newest-first with pagination.

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

Conciseness5/5

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

Three tight sentences, each doing distinct work: what it returns, why the single-call design matters, and the redaction caveat. The purpose and output shape are front-loaded before the caveats, with no filler.

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?

No output schema exists, yet the description still tells the agent what comes back (delivery-status counts, contacts involved, most recent alert, then a page of alerts), plus pagination ordering and the redaction rule. Combined with the annotations, an agent has everything needed to call this correctly.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds real meaning on top: it clarifies that the returned page is the 'newest page of sent alerts', which establishes the ordering that the limit and cursor parameters operate on, and the summary is front-loaded ahead of that page.

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?

States a concrete verb and resource: 'Read the alerts sent during an incident', and even describes the shape of the output (summary plus newest page). It is clearly distinct from list-incidents or get-incident-activity-log by virtue of being about sent alerts specifically, though it never names a sibling to contrast with explicitly.

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?

Offers an implied use case in question form ('were alerts sent, and to whom?') and notes it works 'in one call even on an incident with thousands of notifications', which signals when this beats paging through raw notifications. There is no explicit when-not guidance and no named alternative, so selection still requires inference.

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