Skip to main content
Glama

mcp-uptimerobot__get-response-times

Read-onlyIdempotent

Get response time data for a specific monitor within a time range. Returns time series data with statistical summaries for AI analysis. 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-response-times"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idNoSite to run this tool on: 0b6d9b21-ca64-4476-bc68-d1cd935ca7cb (https://mcp.uptimerobot.com/mcp)
monitorIdYesMonitor ID to get response times for
timeRangeNoTime range for data retrieval. Relative format: "1h" to "90d" (e.g., "24h", "7d"). Absolute format: ISO 8601 interval "startDate/endDate" (e.g., "2024-01-01T00:00:00Z/2024-01-31T23:59:59Z"). Defaults to "7d" (last 7 days).7d
bucketSizeNoOptional bucket size in seconds for time aggregation

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?

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the third sentence ('its server marks it read-only, so it runs straight away') mostly restates structured data rather than adding to it. The genuinely additive part is 'Returns time series data with statistical summaries', which tells the agent the shape of the result, though nothing is said about volume, pagination, or empty ranges.

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 front-loaded and efficient, but the third sentence about 'Royally' and the server's read-only marking is awkwardly worded and largely redundant with the annotations. It spends words on metadata rather than on the return payload the agent cares about.

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?

With no output schema, the description usefully notes that the result is time series data with statistical summaries, which is the key unknown for this tool. The parameter surface is fully covered by the schema, so the remaining gap is minor — mostly the absence of any note on data volume or granularity tradeoffs with bucketSize.

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 monitorId, timeRange, bucketSize and site_id are already documented with formats and defaults. The description adds no syntax, constraints, or examples beyond what the schema supplies, which is the baseline case for full coverage.

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 description states a specific verb and resource ('Get response time data') and scopes it to 'a specific monitor within a time range', which is unambiguous. It stops short of distinguishing itself from the nearby mcp-uptimerobot__get-monitor-stats sibling, so an agent must infer the boundary itself.

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: the phrase 'for a specific monitor within a time range' tells the agent what inputs are needed to invoke it, but there is no explicit statement of when to pick this over get-monitor-stats or get-monitor-details. No exclusions or prerequisites are given.

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