Skip to main content
Glama

mcp-uptimerobot__search-third-party-providers

Read-onlyIdempotent

Search the catalog of third-party providers (cloud, payment and other services whose status pages UptimeRobot can track). Each row has the provider id, the state, the component the search matched and whether this account already tracks the provider. The provider id identifies the provider everywhere else. 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": {
      "search": "<search>"
    },
    "name": "mcp-uptimerobot__search-third-party-providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of providers to return (1-50)
searchYesProvider or component name to search the catalog for
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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuine behavioral detail beyond them: each row includes provider id, state, the matched component, and whether the account already tracks the provider — this account-specific 'tracked' flag is not inferable from annotations. The 'server marks it read-only, so it runs straight away' sentence largely restates the annotation and is the one redundant addition.

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?

Purpose and scope are front-loaded in the first clause, and each subsequent sentence adds return-shape or workflow detail. The closing 'Through Royally' sentence is the only weakly justified content, being mostly meta-commentary on the read-only annotation.

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 carries the burden of explaining return values and does so reasonably (id, state, matched component, tracked flag). For a three-parameter, read-only search with full schema coverage and annotations, an agent has enough to call it and interpret results; only pagination/limit semantics are unaddressed.

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 the schema already documents search, limit and site_id. The description adds a small amount of meaning by implying that search matches component names ('the component the search matched'), but says nothing about limit/pagination behavior, so the baseline of 3 is appropriate.

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 names a specific verb and resource ('Search the catalog of third-party providers') and clarifies the domain with concrete examples (cloud, payment services whose status pages UptimeRobot can track). It also explains what a result row contains, which lets an agent distinguish this from the singular get-third-party-provider siblings, though it never names an alternative explicitly.

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 provider id identifies the provider everywhere else' hints that this tool is the entry point for discovering an id used by other tools. There is no explicit when-to-use/when-not statement and no named alternative, so the agent must infer the workflow.

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