PingRelay MCP Server

monitor_regions_list

Read-onlyIdempotent

List the shared monitor execution-region catalog ordered by name, returning RegionSlug, RegionName, and CountryCode. This is not inferred from configured monitors; use MonitorSettingsGet to inspect a monitor's selected regions. Requires an authenticated organization.

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": "monitor_regions_list"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.7/5.0

Behavior4/5

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

The annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the description isn't burdened with those. It adds real value on top: the result is name-ordered, the exact returned fields, the authentication requirement, and the semantic scope (a shared global catalog rather than per-monitor configuration). It doesn't mention whether the catalog ever varies by org tier or gets cached, but that is a minor omission.

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?

Three short sentences, front-loaded with the action and result shape, then the disambiguation, then the auth prerequisite. Every sentence adds a distinct fact; nothing is repeated from the name or annotations.

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?

For a zero-parameter, read-only catalog listing, the agent needs to know what it returns, how it's ordered, how it differs from the settings tool, and that auth is required — all present. No output schema exists, and the description fills that gap by listing the returned fields.

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?

The tool takes no parameters, so the baseline is 4 and the description correctly spends no words on parameter syntax. Its enumeration of return fields compensates for the absence of an output schema rather than duplicating an input schema.

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 names a specific verb and resource ("List the shared monitor execution-region catalog"), states the ordering (by name) and the exact return fields (RegionSlug, RegionName, CountryCode). It also rules out a plausible misreading by pointing to MonitorSettingsGet, so an agent can separate this catalog lookup from per-monitor region inspection without opening any schema.

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

Usage Guidelines5/5

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

It gives an explicit when-not ("This is not inferred from configured monitors") and names the alternative for the other case (MonitorSettingsGet to inspect a monitor's selected regions). The prerequisite ("Requires an authenticated organization") is stated up front, leaving no ambiguity about eligibility.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PingRelay MCP Server tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?