Skip to main content
Glama

mcp-uptimerobot__get-alert-contact

Read-onlyIdempotent

Get a single personal alert contact by ID. This covers personal channels only — integrations are a separate resource, read via list-integrations. 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": {
      "alertContactId": "<alertContactId>"
    },
    "name": "mcp-uptimerobot__get-alert-contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idNoSite to run this tool on: 0b6d9b21-ca64-4476-bc68-d1cd935ca7cb (https://mcp.uptimerobot.com/mcp)
alertContactIdYesID of the personal alert contact to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description's only behavioral addition is that it 'runs straight away' without confirmation — the rest restates read-only, which the annotations already say. It says nothing about behavior on a nonexistent or out-of-scope ID.

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?

Three tight sentences with the core purpose front-loaded and the scope caveat immediately after. The final sentence about the server marking it read-only is largely redundant with the annotations and could be trimmed without losing 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?

For a simple single-record read with fully described parameters and complete annotations, the definition covers purpose, scope, and the sibling alternative. The one gap is that no output schema exists and the description does not say what fields the returned alert contact contains.

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 both alertContactId and the fixed site_id enum are already documented in the schema. The description's 'by ID' adds nothing beyond the schema, so the baseline 3 applies.

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 ('Get a single personal alert contact by ID') and immediately scopes it: personal channels only, integrations excluded. An agent can distinguish it from list-alert-contacts and from integration lookups without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear exclusion plus the alternative route for the excluded case ('integrations are a separate resource, read via list-integrations'). It does not spell out a when-not condition for the ID lookup itself or name the list sibling, but the single-by-ID framing makes the usage context unambiguous.

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