Skip to main content
Glama

mcp-uptimerobot__get-psp-announcement

Read-onlyIdempotent

Get a single status page announcement by ID. Requires a plan with the psp-subscribers feature. 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>",
      "announcementId": "<announcementId>"
    },
    "name": "mcp-uptimerobot__get-psp-announcement"
  }
}

Input Schema

NameRequiredDescriptionDefault
pspIdYesID of the status page the announcement belongs to
site_idNoSite to run this tool on: 0b6d9b21-ca64-4476-bc68-d1cd935ca7cb (https://mcp.uptimerobot.com/mcp)
announcementIdYesID of the announcement to retrieve

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?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description still adds genuine value beyond those fields: the psp-subscribers plan entitlement is an access precondition an agent must know before calling, and the note that the server marks it read-only explains why execution proceeds without a confirmation step.

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

Conciseness5/5

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

Three short sentences, front-loaded with the core action, then the entitlement prerequisite, then the execution note. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-resource read with full annotation coverage and a 100%-documented schema, the definition is adequate to invoke correctly. However, there is no output schema, so a brief note on what an announcement object contains (title, status, date range) would have closed the remaining gap.

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 both required integer IDs and the site_id enum are already documented. The description adds nothing about pspId or announcementId beyond 'by ID', so the baseline 3 applies — the schema does all the work here.

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 description uses a specific verb and resource: 'Get a single status page announcement by ID.' The word 'single' implicitly contrasts with the sibling list-psp-announcements, though that sibling is never named, so differentiation is inferred rather than stated.

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?

Usage is only implied — an agent can infer it should call this when it already has an announcement ID. The prerequisite 'Requires a plan with the psp-subscribers feature' is real context, but there is no explicit statement about when to prefer this over list-psp-announcements or what to do if the ID is unknown.

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