Skip to main content
Glama

mcp-uptimerobot__get-third-party-service-incident

Read-onlyIdempotent

Get one incident of a tracked third-party service by its monitor ID and incident ID, as listed by list-third-party-service-incidents: title, description, severity, start and resolution time, the provider status updates and the affected components. Only for third-party service incidents, use get-incident-details 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"
  }
}

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.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 sentence 'its server marks it read-only, so it runs straight away' largely restates that in prose (though it does add the practically useful detail that no approval prompt intervenes). The enumeration of returned fields adds real behavioral value since there is no output schema. Left unaddressed: behavior for unknown/invalid IDs and whether the provider status updates are truncated.

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 sentences, front-loaded with the identity of the resource and its return payload, followed by the sibling routing rule. Core content is efficient, though the trailing 'Through Royally: its server marks it read-only, so it runs straight away' is meta-commentary that mostly duplicates the annotation.

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 compensates well by spelling out the returned fields, and it covers ID provenance, sibling routing and safety for a simple single-record read. Minor gaps remain around error/not-found behavior and the slight mismatch in where monitorId is obtained.

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 monitorId and incidentId are already documented with their provenance and format; baseline 3 applies. The description adds little beyond naming the two IDs, and it slightly muddies provenance by tying both to list-third-party-service-incidents while the schema sources monitorId from list-third-party-services.

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 ('Get one incident of a tracked third-party service') and pins the identity keys (monitor ID + incident ID), then enumerates what comes back: title, description, severity, start/resolution time, provider status updates, affected components. It explicitly contrasts itself with get-incident-details, so an agent can distinguish it from the closest sibling without opening either 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?

Gives an explicit inclusion rule ('Only for third-party service incidents') plus the named alternative and its selection condition ('use get-incident-details for incidents of other monitors'). It also routes the agent to the listing tools that supply both IDs, so the retrieval path is fully specified.

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