Skip to main content
Glama

uptimerobot_get_monitors

Read-onlyIdempotent

List UptimeRobot monitors with optional name or URL filtering, and identify any monitors currently DOWN.

Instructions

List UptimeRobot monitors (signals when any are DOWN).

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": {
      "api_key": "<api_key>"
    },
    "name": "uptimerobot_get_monitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoFilter monitors by name or URL
api_keyYesUptimeRobot API key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld behavior, so the safety profile is covered. The description adds useful behavioral context by saying results signal when monitors are DOWN, but it omits pagination, return shape, and any rate-limit or auth nuances beyond the schema-covered api_key.

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?

A single sentence front-loads the verb and resource, and the parenthetical adds the key behavioral signal with no wasted text.

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 listing tool with fully documented parameters and annotations covering safety semantics, this is nearly complete. Only return format and pagination details are absent, but the description at least signals that DOWN statuses are surfaced.

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%, with both the optional 'search' filter and required 'api_key' documented in the schema. The description adds no parameter syntax, examples, or filtering details beyond what the schema already provides, so baseline 3 is appropriate.

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?

States a specific verb ('List') and resource ('UptimeRobot monitors') and adds 'signals when any are DOWN' so an agent knows the tool returns monitor statuses. It does not explicitly name the sibling uptimerobot_get_account or explain the boundary, so it falls short of a 5.

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 parenthetical implies the tool is useful for spotting DOWN monitors, but there is no explicit when-to-use/when-not guidance or named alternative. Usage must be inferred rather than directed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools