Skip to main content
Glama

mcp-uptimerobot__get-user

Read-onlyIdempotent

Names the account and team this MCP session acts on: the signed-in person's email and full name, the monitor count and limit, the third-party service count and limit, SMS credits and active subscription for the session account, and whether this session may write to it. The session account is chosen at OAuth authorization — re-authorize to change it. An API-key session always acts on the key owner's own account; reaching a team account needs OAuth. Personal alert contacts are always the signed-in person's own; everything else belongs to the session account. Call this before a destructive call to confirm which account it will act on. 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-user"
  }
}

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.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. Beyond those, the description adds real behavioral semantics the annotations do not carry: how the session account is bound at OAuth authorization, that re-authorizing is the only way to change it, the API-key OAuth limitation, and that personal alert contacts always belong to the signed-in person. The closing note about Royally marks the tool read-only, which repeats the annotation rather than adding to it.

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?

The description front-loads its purpose in the first clause, then adds usage and caveats, so an agent skimming it will find what it needs immediately. The long enumeration in the first sentence is dense but well organized; however, the final sentence about Royally partly restates the readOnly annotation and takes up space that is mostly redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 has to describe the return values itself, and it does so field by field. It also covers session and identity scoping, which is the main complexity of this tool. An agent has everything it needs in order to call this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is only one parameter, site_id; the schema describes it at 100% coverage with an enum of a single site, and it is not required. Per the baseline rule for zero-or-few parameters with full coverage, the schema already carries the semantics, and the description adds nothing further about site_id, so a 4 is appropriate.

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 opens with a specific verb and resource: it names who the account and team are, and it enumerates the exact fields returned (email, full name, monitor count and limit, third-party service count and limit, SMS credits, subscription, write permission). This is enough to distinguish the tool from the many get-* and list-* siblings, which would otherwise be hard to tell apart.

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?

It gives an explicit when-to-use rule: "Call this before a destructive call to confirm which account it will act on." It also states the preconditions for reaching a team account: "An API-key session always acts on the key owner's own account; reaching a team account needs OAuth". It never says when not to use the tool, nor which sibling to use to get an individual alert contact's or monitor's details; those gaps keep it at a 4.

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