Skip to main content
Glama

mcp-uptimerobot__list-alert-contacts

Read-onlyIdempotent

List the personal alert contacts (email, Pro SMS, voice, iOS/Android push) owned by the authenticated user. This covers personal channels only — integrations (Slack, webhooks, PagerDuty, and similar) are a separate resource, read via list-integrations. In a team session, a monitor can be assigned the session account's integrations or any team member's personal contacts, as on the dashboard. Through Royally: its server marks it read-only, so it runs straight away.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mcp-uptimerobot__list-alert-contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of alert contacts to return (1-200, default 50)
cursorNoPagination cursor for next page
site_idNoSite to run this tool on: 0b6d9b21-ca64-4476-bc68-d1cd935ca7cb (https://mcp.uptimerobot.com/mcp)

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 readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: it confirms the server marks it read-only so it executes immediately without confirmation, and explains the team/session ownership model. It does not describe pagination behavior or the shape of returned contacts, which keeps it short of a 5.

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 front-loaded sentences with the scope and channel list first, then the sibling exclusion, then session behavior. The closing "Through Royally: its server marks it read-only, so it runs straight away" is slightly awkward and partially redundant with the annotations, but it still carries execution information.

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 paginated list tool with a fully documented schema, no output schema, and complete annotations, the description covers what the tool returns at a conceptual level and how it differs from integrations. Pagination expectations and the contact record fields are left entirely to the schema, which is acceptable given its coverage.

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%, and both limit and cursor are documented in the schema with defaults and ranges. The description adds no parameter-level detail such as ordering or filtering, so the baseline of 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 with scope: "List the personal alert contacts (email, Pro SMS, voice, iOS/Android push) owned by the authenticated user." It also explicitly distinguishes itself from the integrations sibling tool, so an agent can separate the two 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 exclusion and the alternative: personal channels only, while "integrations (Slack, webhooks, PagerDuty, and similar) are a separate resource, read via list-integrations." It further clarifies the team-session assignment model so the agent knows which contacts are relevant to a monitor.

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