PingRelay MCP Server

monitor_get

Read-onlyIdempotent

Get a non-deleted monitor summary and effective state by external GUID in the authenticated organization. Use MonitorSettingsGet for configuration, MonitorNotificationsGet for integration routing, and MonitorLatestChecks for completed checks. LastCheckedAt reflects stored scheduled execution time.

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": {
      "monitorExternalId": "<monitorExternalId>"
    },
    "name": "monitor_get"
  }
}

Input Schema

Name	Required	Description	Default
`monitorExternalId`	Yes	External monitor GUID returned as Id by MonitorList or MonitorListRecent; not the internal numeric database ID.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

addedInput schema / properties / monitorExternalId / description

Added value: +"External monitor GUID returned as Id by MonitorList or MonitorListRecent; not the internal numeric database ID."

First observedNov 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real context beyond them: results are limited to non-deleted monitors, the payload is a summary plus 'effective state', and LastCheckedAt is the stored scheduled execution time rather than an actual check completion time — a nuance that prevents misreading the response.

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, purpose front-loaded, then alternatives, then one semantic caveat — nothing wasted. Minor deduction: the sibling tools are cited in PascalCase (MonitorSettingsGet, MonitorLatestChecks) while the actual tool names are snake_case (monitor_settings_get, monitor_latest_checks), which adds a small mapping burden.

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 single-parameter read tool with rich annotations and no output schema, this covers what an agent needs: what it returns (summary + effective state), which monitors are eligible, how to obtain the ID, and which siblings to use instead. Only a note on error behavior for unknown or deleted GUIDs is missing.

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 itself already explains that this is the external GUID returned as Id by MonitorList/MonitorListRecent, not the internal numeric ID. The description only restates 'external GUID', adding no new syntax or format guidance, so 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 non-deleted monitor summary and effective state'), the exact lookup key ('by external GUID'), and the scope ('in the authenticated organization'). The 'non-deleted' qualifier also rules out archived monitors, which separates it from a generic record fetch.

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?

Explicitly routes adjacent needs to three named alternatives: MonitorSettingsGet for configuration, MonitorNotificationsGet for integration routing, MonitorLatestChecks for completed checks. An agent can pick between these without opening any schema.

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?