Skip to main content
Glama

mcp-uptimerobot__get-third-party-service

Read-onlyIdempotent

Get one tracked third-party service by its monitor ID: the provider, current state, notification settings, tracked components and the provider component list. Not for other monitor types, use get-monitor-details for those. 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": {
      "monitorId": "<monitorId>"
    },
    "name": "mcp-uptimerobot__get-third-party-service"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idNoSite to run this tool on: 0b6d9b21-ca64-4476-bc68-d1cd935ca7cb (https://mcp.uptimerobot.com/mcp)
monitorIdYesMonitor ID of the third-party service, from list-third-party-services

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 and destructiveHint=false, so 'its server marks it read-only, so it runs straight away' largely restates what structured data provides. The genuinely additive behavioral content is the enumeration of returned fields, which tells the agent this is a rich single-record fetch rather than a summary. No information about error behavior or missing-service handling is offered.

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?

Two sentences, front-loaded with the verb and resource, with the exclusion placed after the primary statement where it belongs. The trailing Royally/read-only clause is the one piece that arguably does not earn its place since annotations already say so.

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?

There is no output schema, so the description carries the job of describing returns, and it does so by naming the specific fields available. Combined with full schema coverage on inputs, an agent has enough to call it correctly; only error and edge-case behavior is unspecified, which is minor for a read-only single-record fetch.

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% and the schema already explains that monitorId comes from list-third-party-services, so the description's restatement of the ID adds no new meaning. The site_id parameter is not addressed in the description at all, though its enum makes it self-explanatory. Baseline 3 applies when the schema carries the parameter burden.

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+resource ('Get one tracked third-party service by its monitor ID') and enumerates what comes back: provider, current state, notification settings, tracked components and provider component list. It also explicitly names the sibling it is not for, so an agent can distinguish it without opening a schema.

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 an explicit exclusion ('Not for other monitor types') and routes to the correct alternative ('use get-monitor-details for those'). It also points at list-third-party-services as the source of the required ID, so the lookup path is fully determined.

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