Skip to main content
Glama

mcp-uptimerobot__list-psps

Read-onlyIdempotent

List public status pages for the authenticated user. 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

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-psps"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor (status page ID) for the 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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the line "its server marks it read-only, so it runs straight away" largely restates that. The only additional behavioral fact is the cursor-based pagination model; nothing is said about page size, ordering, or what fields a returned status page contains.

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 two sentences are tight and front-loaded with purpose then pagination. The third sentence, "Through Royally: its server marks it read-only, so it runs straight away," is vendor wrapper prose that duplicates the annotation and does not earn its place.

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 read-only list tool with no output schema and fully documented parameters, the definition covers purpose, scope, and pagination adequately. Only the shape of returned items is left unstated, which is minor for a list endpoint.

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 parameters are already documented; the description's cursor sentence merely echoes the schema's "Pagination cursor (status page ID) for the next page". No extra meaning is added for site_id, so baseline 3 applies.

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?

"List public status pages for the authenticated user" names a specific verb (list) and resource (public status pages) and adds a scope constraint (authenticated user's pages). It does not explicitly distinguish itself from get-psp, but the list-vs-single distinction is inferable from the verb.

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 gives one concrete usage instruction: pass the returned cursor to fetch the next page, which sets up pagination workflow. It offers no when-not guidance or explicit alternative (e.g., use get-psp for a single page's details), leaving selection context implied.

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