Skip to main content
Glama

mcp-uptimerobot__get-storm-protection-settings

Read-onlyIdempotent

Get the account-wide storm protection (alert grouping) settings: whether it is enabled, the threshold type and value, the time window, and whether alerts are pooled. Returns defaults when not yet configured. 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__get-storm-protection-settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4/5.0
Behavior4/5

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

It goes beyond simple annotations by explicitly stating a key behavior: 'Returns defaults when not yet configured.' Furthermore, it provides useful operational context that confirms the safety profile ('its server marks it read-only, so it runs straight away.' ), reinforcing the hints.

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?

The description is highly efficient, front-loading the core purpose and then detailing the contents and execution context. Every sentence provides distinct, valuable information.

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?

The definition is highly complete. It explains the purpose, the nature of the returned data (including defaults), and the operational safety of the tool. Given the simple schema, no missing information is critical for correct invocation.

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?

With 100% schema description coverage, the parameter 'site_id' is fully documented by the schema. The description does not need to add semantic meaning to a single, clearly defined input parameter, meeting the baseline minimum for full coverage.

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?

The description immediately identifies the resource and function: 'Get the account-wide storm protection (alert grouping) settings.' It specifies the exact types of settings returned (enabled, threshold, time window, pooling).

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 focuses heavily on *what* the tool returns rather than providing explicit comparisons or warnings regarding when *not* to use it. The usage is heavily implied by the specific nature of the settings it accesses.

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