Skip to main content
Glama

mcp-uptimerobot__list-third-party-services

Read-onlyIdempotent

List the third-party services this account tracks (monitors of the third-party service type), with the current state of each provider. These monitors are not returned by list-monitors. Use get-third-party-service for one service in full. 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-third-party-services"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return per page (default: 10, max: 100)
cursorNoPagination cursor for next page
searchNoMatches the service name or its status page URL
site_idNoSite to run this tool on: 0b6d9b21-ca64-4476-bc68-d1cd935ca7cb (https://mcp.uptimerobot.com/mcp)
sortFieldNoField to sort by, default order when omitted
sortDirectionNoSort direction, ASC when a sortField is given without one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 most behavior is structured. The description adds only that results include each provider's current state, and the 'Through Royally: its server marks it read-only' sentence largely restates the readOnlyHint already provided; it does not cover pagination behavior despite cursor/limit params.

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?

Front-loaded with the strongest disambiguator ('not returned by list-monitors') and only three sentences. The closing Royally sentence is slightly odd and adds little, but it is short and does not obscure the core guidance.

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 six-param, all-optional list tool with full schema coverage and no output schema, the description covers purpose, sibling routing, and result content adequately. It stops short of explaining pagination or sort interplay, but nothing critical to correct invocation 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?

The description says nothing about the limit, cursor, search, sortField, or sortDirection parameters. With schema description coverage at 100%, the schema already carries all parameter meaning, so the baseline 3 applies and the description neither helps nor harms.

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 ('List the third-party services this account tracks') and narrows it to 'monitors of the third-party service type', plus what each entry contains ('current state of each provider'). It explicitly distinguishes itself from list-monitors, so an agent can separate the two without inspecting schemas.

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 both routing conditions: the items 'are not returned by list-monitors' and 'Use get-third-party-service for one service in full'. That names the closest sibling alternatives and the condition that selects them, leaving little to inference.

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