Skip to main content
Glama

mcp-uptimerobot__list-psp-announcements

Read-onlyIdempotent

List announcements for a public status page. Requires a plan with the psp-subscribers 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": {
      "pspId": "<pspId>"
    },
    "name": "mcp-uptimerobot__list-psp-announcements"
  }
}

Input Schema

NameRequiredDescriptionDefault
pspIdYesID of the status page whose announcements to list
cursorNoPagination cursor (announcement ID) for the next page
statusNoOptional filter by status
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so the closing 'server marks it read-only' sentence merely repeats structured data. The genuinely additive content is the plan/entitlement requirement and the cursor-based pagination protocol, which the annotations do not express. There is no contradiction, but the description spends one sentence on redundant safety restatement.

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?

Four short, front-loaded sentences: purpose first, then prerequisite, then pagination, then a safety note. The final sentence about 'Royally' and read-only is largely wasted given the annotations, but the rest is tight.

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 four-parameter, fully documented list tool with no output schema, the description covers purpose, entitlement gate, and pagination. The only remaining ambiguity is how paging terminates, which is minor at this complexity.

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%, documenting pspId, cursor, status enum and site_id, so the schema already carries the parameter burden. The description only adds that the cursor is a value returned by a prior call, which is a small but real semantic addition over the cursor field's own text.

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 opening sentence gives a precise verb+resource ('List announcements for a public status page'), which is enough for an agent to separate it from the singular get-psp-announcement and from list-psps. It stops short of naming any sibling explicitly, so it is clear but not maximally differentiating.

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 supplies two real usage conditions: the psp-subscribers plan feature is required, and the returned cursor must be passed back to page. It gives no guidance on when to prefer this over get-psp-announcement or list-psps, and no note about when to stop paging, so usage is implied rather than fully directed.

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