Skip to main content
Glama

mcp-uptimerobot__get-third-party-provider

Read-onlyIdempotent

Get a third-party provider by ID: its name, status page, current state and the component tree. Component IDs from here select the components to track. 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": {
      "providerId": "<providerId>"
    },
    "name": "mcp-uptimerobot__get-third-party-provider"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idNoSite to run this tool on: 0b6d9b21-ca64-4476-bc68-d1cd935ca7cb (https://mcp.uptimerobot.com/mcp)
providerIdYesProvider ID, from search-third-party-providers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The added sentence "its server marks it read-only, so it runs straight away" restates the read-only annotation in the form of a no-approval-gate consequence, which is mild added value; nothing is said about behavior on an invalid or unknown providerId.

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?

Two compact sentences: what is returned first, then how the result is used. The host-specific "Through Royally" clause is slightly awkward but short and does convey why the call proceeds without confirmation; no filler 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?

No output schema exists, and the description compensates by naming the returned fields, including the component tree that drives the downstream selection use case. For a two-parameter read tool with full annotation coverage this is close to complete; only error/empty-result behavior is unstated.

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 coverage is 100% and the schema already documents providerId as coming from search-third-party-providers and site_id as the target site. The description adds no format, valid-range, or error semantics beyond that, so the baseline 3 for schema-covered parameters applies.

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?

Specific verb and resource ("Get a third-party provider by ID") plus an enumeration of the returned fields – name, status page, current state, component tree – which lets an agent distinguish it from the list/search siblings. It does not, however, differentiate it from mcp-uptimerobot__get-third-party-service, which an agent may easily confuse it with given the near-identical naming.

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 phrase "Component IDs from here select the components to track" supplies a genuine downstream use case, and the schema points providerId back to search-third-party-providers. But there is no explicit statement of when to call this versus get-third-party-service or the list tools, leaving the agent to infer the provider/service distinction.

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