Skip to main content
Glama

mcp-uptimerobot__get-incident-details

Read-onlyIdempotent

Get comprehensive incident details including checker locations, IPs, logs, and traceroute data. Not for third-party service incidents, use get-third-party-service-incident for those. 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-details"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idNoSite to run this tool on: 0b6d9b21-ca64-4476-bc68-d1cd935ca7cb (https://mcp.uptimerobot.com/mcp)
incidentIdYesIncident ID to retrieve details for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The line 'its server marks it read-only, so it runs straight away' mostly restates the annotation rather than adding new behavior, though the enumerated payload data does set expectations about a potentially large, verbose response. Nothing about response size, latency, or missing-incident behavior is disclosed.

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 purpose, then the exclusion/alternative in the second sentence — good ordering. The third sentence about the Royally wrapper is meta-commentary that adds little for an agent and could be trimmed, keeping it short of a 5.

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 two-parameter read tool with no output schema, the description covers purpose, scope boundary, alternative routing, and the kinds of data returned — enough for an agent to call it correctly the first time. Nothing an agent needs to invoke it is missing.

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%, including the incidentId description and the site_id enum with its endpoint URL, so the schema carries all parameter meaning. The description adds no format details for incidentId (e.g., accepted ID shape) beyond what is already documented, so 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 ('Get ... incident details') and enumerates the payload ('checker locations, IPs, logs, and traceroute data'), which lets an agent distinguish it from get-incident-activity-log or get-incident-alerts without opening schemas. It also names the sibling it is not (get-third-party-service-incident).

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 exclusion ('Not for third-party service incidents') and the exact alternative to use instead, which is the strongest form of routing guidance. The read-only note also implies it is safe to call speculatively, reinforcing when to reach for 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