Skip to main content
Glama

mcp-uptimerobot__get-psp

Read-onlyIdempotent

Get a single public status page by ID. 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__get-psp"
  }
}

Input Schema

NameRequiredDescriptionDefault
pspIdYesID of the public status page to retrieve
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is fully covered structurally. The description adds that the call runs without an approval round-trip ('it runs straight away'), which is genuinely useful operational context, but the phrasing 'Through Royally: its server marks it read-only' is opaque and conveys little else about results or failure modes.

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?

It is short and front-loads the action, which is good. The second sentence is cryptic shorthand ('Through Royally') that costs space without delivering clear meaning to an agent.

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 simple single-record read with complete annotation coverage, full schema descriptions, and no output schema to explain, the definition supplies what is needed to call it correctly. Only a pointer to the listing sibling for ID discovery 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 an enum and range constraint on pspId, so the schema already carries the parameter meaning. The description only echoes 'by ID' and adds no format, validity, or behavior detail beyond that baseline.

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 ('Get a single public status page by ID'), which clearly separates it from a bulk-listing call such as list-psps. It stops short of naming a sibling or stating the boundary 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?

Usage is only implied: 'by ID' suggests the caller should already hold a page ID, which hints that discovery should go through a list tool first. There is no explicit when-to-use/when-not guidance and no named alternative, leaving the agent to infer routing.

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