Skip to main content
Glama

mcp-uptimerobot__list-incident-comments

Read-onlyIdempotent

List comments on an incident. Requires a plan with the incident-comments feature. Pass the returned cursor to fetch the next page. 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__list-incident-comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of comments to return (1-100, default 50)
cursorNoPagination cursor (comment ID) for the next page
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

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful non-annotation context: the entitlement gate on the plan and the fact that a cursor is returned for subsequent pages. The trailing "Through Royally: its server marks it read-only, so it runs straight away" largely restates the annotation rather than adding new behavior.

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

Conciseness3/5

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

The first three clauses are tight and front-loaded, but the final sentence about the Royally server and read-only status duplicates the readOnlyHint annotation and adds little. The description is short overall, but roughly a quarter of it is redundant.

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?

For a read-only paginated list tool with no output schema and fully documented parameters, most of what an agent needs is present: the resource, the entitlement requirement, and the pagination protocol. What is missing is any hint about the shape of a returned comment or how failures surface when the plan lacks the feature.

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 description coverage is 100%, so the baseline would be 3. The description earns an extra point by explaining the cursor's cross-call contract: it is returned by the tool and should be passed back to fetch the next page, which the schema alone does not convey.

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?

The first sentence gives a specific verb and resource ("List comments on an incident"), which is clear enough to distinguish it from siblings like get-incident-alerts. It lacks any explicit contrast with overlapping tools such as get-incident-activity-log, so it stops short of full sibling differentiation.

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?

The description states a concrete prerequisite (a plan with the incident-comments feature) and explains the pagination loop via the returned cursor, which is useful operating guidance. However, it never says when to choose this over get-incident-activity-log or how it differs from other incident sub-resources.

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