Skip to main content
Glama

mcp-uptimerobot__get-third-party-service-incident-activity-log

Read-onlyIdempotent

List the notifications this account was sent about one incident of a tracked third-party service, by its monitor ID and incident ID from list-third-party-service-incidents: the channel, the recipient, the alert contact, whether it was delivered and when. Recipients are shown in full only for email, SMS and voice contacts, every other type is "[REDACTED]". Empty when nothing was sent. Only for third-party service incidents, use get-incident-activity-log for incidents of other monitors. 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": {
      "monitorId": "<monitorId>",
      "incidentId": "<incidentId>"
    },
    "name": "mcp-uptimerobot__get-third-party-service-incident-activity-log"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idNoSite to run this tool on: 0b6d9b21-ca64-4476-bc68-d1cd935ca7cb (https://mcp.uptimerobot.com/mcp)
monitorIdYesMonitor ID of the third-party service, from list-third-party-services
incidentIdYesIncident ID, a numeric string from list-third-party-service-incidents

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description still adds real behavior the annotations cannot express — recipient redaction for all non-email/SMS/voice channels and an empty result when nothing was sent. The closing note about running straight away merely restates the read-only annotation in practical terms, and it says nothing about ordering, pagination, or volume for what is a log endpoint.

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 action and scope, then short sentences for redaction, empty case, and the sibling exclusion. The trailing 'Through Royally: its server marks it read-only, so it runs straight away' adds little beyond the annotation and is the one sentence that could be dropped.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and does it well by enumerating the fields returned (channel, recipient, alert contact, delivery status and time) plus the redaction rule. The remaining gap is operational: no hint on ordering, result volume, or whether the log can be truncated for a long-running incident.

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 schema already documents monitorId and incidentId, including the numeric-string pattern and the originating list tool. The description restates the same provenance and adds no format, range, or edge-case detail beyond it, so the baseline 3 applies.

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 — lists the notifications sent about one incident of a tracked third-party service — and pins the scope with the two identifiers it needs. It also explicitly distinguishes itself from get-incident-activity-log and from the incident-list tools, so an agent can route correctly without opening any schema.

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?

Names the exclusion outright: 'Only for third-party service incidents, use get-incident-activity-log for incidents of other monitors.' It also tells the agent where each ID comes from (list-third-party-services for monitorId, list-third-party-service-incidents for incidentId), which is the practical prerequisite for calling it.

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